Benjamin Herrenschmidt writes:
> On Sun, 2012-06-10 at 00:59 +0200, Andreas Schwab wrote:
>> It's a PowerMac G5. During booting I see this:
>
> There's about half a dozen versions of those :-) I assume the older
> PowerMac7,2 ?
Yes, that's right. Sorry for being imprecise.
>> PowerMac i2c bus
On Sun, 2012-06-10 at 09:13 +0200, Andreas Schwab wrote:
> Benjamin Herrenschmidt writes:
>
> > On Sun, 2012-06-10 at 00:59 +0200, Andreas Schwab wrote:
> >> It's a PowerMac G5. During booting I see this:
> >
> > There's about half a dozen versions of those :-) I assume the older
> > PowerMac7,2
Commit 430b01e8f5e524a2bfa50074d97d0bdc2505807b ("[POWERPC] Kill
flatdevtree.c") killed the two files including flatdevtree_env.h. It was
apparently just an oversight to not kill that header too. Kill it now.
Signed-off-by: Paul Bolle
---
Tested with "git grep" only.
arch/powerpc/boot/flatdevtr
Benjamin Herrenschmidt writes:
> Ah, excellent, so a small quirk in i2c_powermac is the way to go then,
> we can detect it by name and hack up something. Either that or even
> better, in prom_init, we could add the missing property to the
> device-tree.
How does that look like? Though I'm not s
Hello,
I'm working on various PMU bits for FreeBSD (I know, not related to
Linux), but running into some problems, which the Linux crowd may be
able to help with, as it's already solved for Linux. I've managed to
get it to sleep for performing the sleep operation and for the CPU speed
switch on M
On Sun, 2012-06-10 at 09:29 -0400, Justin Hibbits wrote:
> Hello,
>
> I'm working on various PMU bits for FreeBSD (I know, not related to
> Linux), but running into some problems, which the Linux crowd may be
> able to help with, as it's already solved for Linux. I've managed to
> get it to sleep
Hi Christoph,
On Mon, Jun 4, 2012 at 8:37 AM, Christoph Fritz
wrote:
> After that, I stumbled upon this dmesg:
>
> Freescale High-Speed USB SOC Device Controller driver (Apr 20, 2007)
> fsl-usb2-udc fsl-usb2-udc: clk_get("usb") failed
> fsl-usb2-udc: probe of fsl-usb2-udc failed with error -2
>
Hi
The P1020 manual states (in the PIC chapter) that in the "Internal Interrupt
Destination" register, only 1 CPU (and not both) can be selected as the IRQ
destination. How then can we achieve "interrupt spraying" for the PCI interrupt
(we want interrupts to be sent alternately to CPU0 and CPU1)
Hi
The P1020 manual states (in the PIC chapter) that in the "Internal Interrupt
Destination" register, only 1 CPU (and not both) can be selected as the IRQ
destination. How then can we achieve "interrupt spraying" for the PCI interrupt
(we want interrupts to be sent alternately to CPU0 and CPU1)
> -Original Message-
> From: Bhushan Bharat-R65777
> Sent: Friday, June 08, 2012 6:47 PM
> To: Jia Hongtao-B38951; linuxppc-dev@lists.ozlabs.org;
> ga...@kernel.crashing.org
> Cc: Li Yang-R58472; b...@kernel.crashing.org; Wood Scott-B07421
> Subject: RE: [PATCH 0/6] Description for PCI patc
On Mon, 11 Jun 2012 09:03:13 +1000
Benjamin Herrenschmidt wrote:
> On Sun, 2012-06-10 at 09:29 -0400, Justin Hibbits wrote:
> > Hello,
> >
> > I'm working on various PMU bits for FreeBSD (I know, not related to
> > Linux), but running into some problems, which the Linux crowd may be
> > able to
11 matches
Mail list logo
