On Wed, 10 Oct 2007 10:30:02 +0200
Stefan Roese <[EMAIL PROTECTED]> wrote:
> On Wednesday 10 October 2007, Arnd Bergmann wrote:
> > > Do PPC folk sign off on how this is done?
> > >
> > > I don't follow all the ins/outs of the OF devtree stuff...
> >
> > The driver looks good to me, both the inter
On Wednesday 10 October 2007, Arnd Bergmann wrote:
> > Do PPC folk sign off on how this is done?
> >
> > I don't follow all the ins/outs of the OF devtree stuff...
>
> The driver looks good to me, both the interaction with the of_platform_bus
> layer and the handling of I/O addresses. I haven't act
On Wednesday 10 October 2007, David Brownell wrote:
> On Monday 24 September 2007, Valentine Barshak wrote:
> > Some PowerPC systems have a built-in EHCI controller.
> > This is a device tree aware version of the EHCI controller driver.
> > Currently it's been tested on the PowerPC 440EPx Sequoia b
On Monday 24 September 2007, Valentine Barshak wrote:
> Some PowerPC systems have a built-in EHCI controller.
> This is a device tree aware version of the EHCI controller driver.
> Currently it's been tested on the PowerPC 440EPx Sequoia board.
> Other platforms can be added later.
> The code is ba
Valentine Barshak wrote:
> Jerone Young wrote:
>> So the issue here with the Sequoia board is that if you load a kernel or
>> initrd from usb stick while under u-boot environment, when Linux boots
>> it will see the network adapter & even set an ip for it. But no matter
>> what it is unable to acce
Jerone Young wrote:
> So the issue here with the Sequoia board is that if you load a kernel or
> initrd from usb stick while under u-boot environment, when Linux boots
> it will see the network adapter & even set an ip for it. But no matter
> what it is unable to access any outside ip.
>
> The way
So the issue here with the Sequoia board is that if you load a kernel or
initrd from usb stick while under u-boot environment, when Linux boots
it will see the network adapter & even set an ip for it. But no matter
what it is unable to access any outside ip.
The way we recreated this scenario was:
Some PowerPC systems have a built-in EHCI controller.
This is a device tree aware version of the EHCI controller driver.
Currently it's been tested on the PowerPC 440EPx Sequoia board.
Other platforms can be added later.
The code is based on the ehci-ppc-soc driver by Stefan Roese <[EMAIL
PROTECTE
Hollis Blanchard wrote:
> On Mon, 17 Sep 2007 16:50:39 +0400, Valentine Barshak wrote:
>
>> Some PowerPC systems have a built-in EHCI controller.
>> This is a device tree aware version of the EHCI controller driver.
>> Currently it's been tested on the PowerPC 440EPx Sequoia board.
>> Other platfo
On Mon, 17 Sep 2007 16:50:39 +0400, Valentine Barshak wrote:
> Some PowerPC systems have a built-in EHCI controller.
> This is a device tree aware version of the EHCI controller driver.
> Currently it's been tested on the PowerPC 440EPx Sequoia board.
> Other platforms can be added later.
> The co
Some PowerPC systems have a built-in EHCI controller.
This is a device tree aware version of the EHCI controller driver.
Currently it's been tested on the PowerPC 440EPx Sequoia board.
Other platforms can be added later.
The code is based on the ehci-ppc-soc driver by Stefan Roese <[EMAIL
PROTECTE
11 matches
Mail list logo
