kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #26610
[Bug 1248233] [NEW] [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART
Public bug reported:
There is no earlyprintk via the PL011 because there's no defined device
tree binding for earlyprintk UART to get the PL011 to work you'll need
to tweak the kernel a bit. kernel doesn't ever add the clock to its
list, and then it refuses to probe for the PL011. This is a temporary
fix, ideally the call should be done in some generic location rather
than in every machine's init function.) The alternative would be for the
kernel to be fixed to follow its own device tree binding documentation
and not require clocks/clock-names properties on the pl011 node.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Paolo Pisati (p-pisati)
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1248233
Title:
[saucy][armhf] No early printk because there's no defined device tree
binding for earlyprintk UART
Status in “linux” package in Ubuntu:
New
Bug description:
There is no earlyprintk via the PL011 because there's no defined
device tree binding for earlyprintk UART to get the PL011 to work
you'll need to tweak the kernel a bit. kernel doesn't ever add the
clock to its list, and then it refuses to probe for the PL011. This is
a temporary fix, ideally the call should be done in some generic
location rather than in every machine's init function.) The
alternative would be for the kernel to be fixed to follow its own
device tree binding documentation and not require clocks/clock-names
properties on the pl011 node.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248233/+subscriptions
Follow ups
-
[Bug 1248233] Re: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART
From: Launchpad Bug Tracker, 2014-01-02
-
[Bug 1248233] Re: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART
From: Manoj Iyer, 2013-12-13
-
[Bug 1248233] Re: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART
From: Brad Figg, 2013-12-13
-
[Bug 1248233] Re: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART
From: Brad Figg, 2013-12-09
-
[Bug 1248233] Re: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART
From: Launchpad Bug Tracker, 2013-12-05
-
[Bug 1248233] Re: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART
From: Manoj Iyer, 2013-11-07
-
[Bug 1248233] Re: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART
From: Paolo Pisati, 2013-11-06
-
[Bug 1248233] Re: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART
From: Ubuntu Foundations Team Bug Bot, 2013-11-05
-
[Bug 1248233] Re: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART
From: Joseph Salisbury, 2013-11-05
-
[Bug 1248233] Missing required logs.
From: Brad Figg, 2013-11-05
-
[Bug 1248233] Re: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART
From: Manoj Iyer, 2013-11-05
-
[Bug 1248233] [NEW] [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART
From: Manoj Iyer, 2013-11-05
References