Re: [linux-usb-devel] [PATCH 0/3] usb: ehci ppc device-tree-aware driver

2007-10-23 Thread Josh Boyer
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 interaction with the of_platform_bus
  layer and the handling of I/O addresses. I haven't actually tried running
  it, but I'm rather confident that if it works on the Sequoia, it should
  also do the right thing on any other powerpc system that has an EHCI on
  some other (non-PCI) bus.
 
  Acked-by: Arnd Bergmann [EMAIL PROTECTED]
 
 Acked-by: Stefan Roese [EMAIL PROTECTED]

David, were you going to pull in the echi-ppc-of driver (patch 1 of
this series) for 2.6.24?  Just trying to figure out if I need to pull
the other two patches into my tree.

josh
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Re: [linux-usb-devel] [PATCH 0/3] usb: ehci ppc device-tree-aware driver

2007-10-10 Thread David Brownell
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 based on the ehci-ppc-soc driver by Stefan Roese [EMAIL 
 PROTECTED].

Do PPC folk sign off on how this is done?

I don't follow all the ins/outs of the OF devtree stuff...
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Re: [linux-usb-devel] [PATCH 0/3] usb: ehci ppc device-tree-aware driver

2007-10-10 Thread Arnd Bergmann
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 board.
  Other platforms can be added later.
  The code is based on the ehci-ppc-soc driver by Stefan Roese [EMAIL 
  PROTECTED].
 
 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 actually tried running
it, but I'm rather confident that if it works on the Sequoia, it should
also do the right thing on any other powerpc system that has an EHCI on
some other (non-PCI) bus.

Acked-by: Arnd Bergmann [EMAIL PROTECTED]
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Re: [linux-usb-devel] [PATCH 0/3] usb: ehci ppc device-tree-aware driver

2007-10-10 Thread Stefan Roese
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 actually tried running
 it, but I'm rather confident that if it works on the Sequoia, it should
 also do the right thing on any other powerpc system that has an EHCI on
 some other (non-PCI) bus.

 Acked-by: Arnd Bergmann [EMAIL PROTECTED]

Acked-by: Stefan Roese [EMAIL PROTECTED]

Best regards,
Stefan
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Re: [PATCH 0/3] usb: ehci ppc device-tree-aware driver

2007-10-08 Thread Jerone Young
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:

- Have a USB stick with
- partition 1 is fat partition with our kernel  initrd
- partition 2 is ext3 with our root filesystem

1) Boot Sequoia board with USB stick plugged in. Go to u-boot prompt.
2) start usb using usb start
3) Load kernel off usb stick using fatload command in uboot
   * Optionally load initrd off of usb stick
   * Example:
  fatload usb 0:1 400 cuImage.sequoia

4) stop usb using usb stop
5) Then boot kernel using bootm

Now from this point linux loads and will mount the filesystem on the usb
stick.  But if you want to use networking in anyway you have a problem.
You can start the telnet daemon and access from the board using
127.0.0.1 address (loopback). Trying to access the telnet from an
outside ip is unsuccessful.

Also, if you have it setup so that the root filesystem is on a nfs root,
the kernel is never able to get to the nfs root. Basically something is
really borked.

I'm a little late getting back to this email :-0

On Sat, 2007-09-22 at 23:00 +, 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 platforms can be added later.
  The code is based on the ehci-ppc-soc driver by Stefan Roese [EMAIL 
  PROTECTED].
 
 We're having a strange issue on our Sequoia where the network stops
 functioning when USB is active. Jerone can supply more detail...
 
 Have you seen anything like that?
 

___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Re: [PATCH 0/3] usb: ehci ppc device-tree-aware driver

2007-10-08 Thread Valentine Barshak
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 we recreated this scenario was:
 
 - Have a USB stick with
 - partition 1 is fat partition with our kernel  initrd
 - partition 2 is ext3 with our root filesystem
 
 1) Boot Sequoia board with USB stick plugged in. Go to u-boot prompt.
 2) start usb using usb start
 3) Load kernel off usb stick using fatload command in uboot
* Optionally load initrd off of usb stick
* Example:
   fatload usb 0:1 400 cuImage.sequoia
 
 4) stop usb using usb stop
 5) Then boot kernel using bootm
 
 Now from this point linux loads and will mount the filesystem on the usb
 stick.  But if you want to use networking in anyway you have a problem.
 You can start the telnet daemon and access from the board using
 127.0.0.1 address (loopback). Trying to access the telnet from an
 outside ip is unsuccessful.
 
 Also, if you have it setup so that the root filesystem is on a nfs root,
 the kernel is never able to get to the nfs root. Basically something is
 really borked.
 
 I'm a little late getting back to this email :-0
 
 On Sat, 2007-09-22 at 23:00 +, 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 platforms can be added later.
 The code is based on the ehci-ppc-soc driver by Stefan Roese [EMAIL 
 PROTECTED].
 We're having a strange issue on our Sequoia where the network stops
 functioning when USB is active. Jerone can supply more detail...

 Have you seen anything like that?

 
Please try this patch:
http://ozlabs.org/pipermail/linuxppc-dev/2007-October/043435.html
Thanks,
Valentine.
 ___
 Linuxppc-dev mailing list
 Linuxppc-dev@ozlabs.org
 https://ozlabs.org/mailman/listinfo/linuxppc-dev

___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Re: [PATCH 0/3] usb: ehci ppc device-tree-aware driver

2007-10-08 Thread Valentine Barshak
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 access any outside ip.

 The way we recreated this scenario was:

 - Have a USB stick with
 - partition 1 is fat partition with our kernel  initrd
 - partition 2 is ext3 with our root filesystem

 1) Boot Sequoia board with USB stick plugged in. Go to u-boot prompt.
 2) start usb using usb start
 3) Load kernel off usb stick using fatload command in uboot
* Optionally load initrd off of usb stick
* Example:
   fatload usb 0:1 400 cuImage.sequoia
 
 4) stop usb using usb stop
 5) Then boot kernel using bootm

 Now from this point linux loads and will mount the filesystem on the usb
 stick.  But if you want to use networking in anyway you have a problem.
 You can start the telnet daemon and access from the board using
 127.0.0.1 address (loopback). Trying to access the telnet from an
 outside ip is unsuccessful.

 Also, if you have it setup so that the root filesystem is on a nfs root,
 the kernel is never able to get to the nfs root. Basically something is
 really borked.

 I'm a little late getting back to this email :-0

 On Sat, 2007-09-22 at 23:00 +, 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 platforms can be added later.
 The code is based on the ehci-ppc-soc driver by Stefan Roese [EMAIL 
 PROTECTED].
 We're having a strange issue on our Sequoia where the network stops
 functioning when USB is active. Jerone can supply more detail...

 Have you seen anything like that?

 Please try this patch:
 http://ozlabs.org/pipermail/linuxppc-dev/2007-October/043435.html
 Thanks,
 Valentine.

Also please, don't forget to uncomment this line:
#   select IBM_NEW_EMAC_RGMII
It's commented out in the original patch since new EMAC support hasn't 
been merged yet.
Thanks,
Valentine.

 ___
 Linuxppc-dev mailing list
 Linuxppc-dev@ozlabs.org
 https://ozlabs.org/mailman/listinfo/linuxppc-dev
 
 ___
 Linuxppc-dev mailing list
 Linuxppc-dev@ozlabs.org
 https://ozlabs.org/mailman/listinfo/linuxppc-dev

___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Re: [PATCH 0/3] usb: ehci ppc device-tree-aware driver

2007-09-24 Thread Valentine Barshak
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 platforms can be added later.
 The code is based on the ehci-ppc-soc driver by Stefan Roese [EMAIL 
 PROTECTED].
 
 We're having a strange issue on our Sequoia where the network stops
 functioning when USB is active. Jerone can supply more detail...

OK.
This possibly could be caused by the plb write pipelining errata.
Please, take a look at:
http://ozlabs.org/pipermail/linuxppc-dev/2007-September/042999.html

 
 Have you seen anything like that?

No, I haven't.

 

Thanks,
Valentine.
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev


Re: [PATCH 0/3] usb: ehci ppc device-tree-aware driver

2007-09-22 Thread Hollis Blanchard
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 code is based on the ehci-ppc-soc driver by Stefan Roese [EMAIL 
 PROTECTED].

We're having a strange issue on our Sequoia where the network stops
functioning when USB is active. Jerone can supply more detail...

Have you seen anything like that?

-- 
Hollis Blanchard
IBM Linux Technology Center

___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev