Problem Regarding Ping in Linux kernel version 2.4.24

Problem Regarding Ping in Linux kernel version 2.4.24

[apoorv sangal]

[-- Attachment #1: Type: text/plain, Size: 678 bytes --]

Hi All,
 I have ported Linux kernel version 2.4.24 on MPC8266 based customized
Board, having LXT971 ethernet chip.
The root file system is JFFS2 which i have made using mkfs.jffs2 utility
which comes along with the ELDK 3.0
In the kernel code i checked that there is support for the LXT971 chip, but
even after enabling all the network related funcuntionalities in the linux
kernel configuration, I am either not able to ping from the board to any
machine on the network, nor from the any other machine to the board.
The board is able to ping itself.
Can some one please throw some light why the board is not able to ping any
other machine.
 Regards
Apoorv Sangal

[-- Attachment #2: Type: text/html, Size: 845 bytes --]

Re: Problem Regarding Ping in Linux kernel version 2.4.24

[Aristeu Sergio Rozanski Filho]

Hi,
>           I have ported Linux kernel version 2.4.24 on MPC8266 based customized
> Board,  having LXT971 ethernet chip.
> The root file system is JFFS2 which i have made using mkfs.jffs2 utility which
> comes along with the ELDK 3.0
> In the kernel code i checked that there is support for the LXT971 chip, but
> even after enabling all the network related funcuntionalities in the linux
> kernel configuration, I am either not able to ping from the board to any
> machine on the network, nor from the any other machine to the board.
> The board is able to ping itself.
> Can some one please throw some light why the board is not able to ping any
> other machine.
try to comment this line in LXT971 section of driver:
	{ mk_mii_write(MII_REG_CR, 0x1200), NULL }, /* autonegotiate */
and check if it works

-- 
Aristeu

Re: Problem Regarding Ping in Linux kernel version 2.4.24

[apoorv sangal]

[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]

Hi
Thanks for the inputs... As per your suggestion I commented
 { mk_mii_write(MII_REG_CR, 0x1200), NULL }, /* autonegotiate */
but it doesn't make any diffrence, still the ping doesn't worked.
 At Boot loader level (u-boot) Ping works fine,
    Regards
Apoorv Sangal


 On 10/7/05, Aristeu Sergio Rozanski Filho <aris@cathedrallabs.org> wrote:
>
> Hi,
> > I have ported Linux kernel version 2.4.24 on MPC8266 based customized
> > Board, having LXT971 ethernet chip.
> > The root file system is JFFS2 which i have made using mkfs.jffs2 utility
> which
> > comes along with the ELDK 3.0
> > In the kernel code i checked that there is support for the LXT971 chip,
> but
> > even after enabling all the network related funcuntionalities in the
> linux
> > kernel configuration, I am either not able to ping from the board to any
> > machine on the network, nor from the any other machine to the board.
> > The board is able to ping itself.
> > Can some one please throw some light why the board is not able to ping
> any
> > other machine.
> try to comment this line in LXT971 section of driver:
> { mk_mii_write(MII_REG_CR, 0x1200), NULL }, /* autonegotiate */
> and check if it works
>
> --
> Aristeu
>
>

[-- Attachment #2: Type: text/html, Size: 1998 bytes --]

Re: Problem Regarding Ping in Linux kernel version 2.4.24

[Mark Chambers]

[-- Attachment #1: Type: text/plain, Size: 534 bytes --]



  Hi 
  Thanks for the inputs... As per your suggestion I commented 
                          { mk_mii_write(MII_REG_CR, 0x1200), NULL }, /* autonegotiate */
  but it doesn't make any diffrence, still the ping doesn't worked.

  At Boot loader level (u-boot) Ping works fine, 


  I think you need to provide more information, because there are many things
  that could be wrong.  Attach the output of your console from the boot sequence,
  and include the output of an ifconfig command if you can.

  Mark Chambers

[-- Attachment #2: Type: text/html, Size: 1650 bytes --]

MPC8555 USB host support

[Stefan Roese]

I am wondering, if the USB host controller of the MPC8555 is supported at all 
right now. The manual states, that it is similar to, but not fully OHCI or 
UHCI compatible. Any infos about this?

Best regards,
Stefan

Re: Problem Regarding Ping in Linux kernel version 2.4.24

[apoorv sangal]

[-- Attachment #1: Type: text/plain, Size: 6390 bytes --]

Hi,
I am sending the output from the console of the boot sequence and ifconfig
command as following.
Please check the same and let me know where i am going wrong.
*******************************************************************************************************
## Total Size = 0x00088c6d = 560237 Bytes

## Start Addr = 0x02000000

=> bootm 02000000 ## Booting image at 02000000 ...

Image Name: 2.4.24 10thOCT3

Image Type: PowerPC Linux Kernel Image (gzip compressed)

Data Size: 560173 Bytes = 547 kB

Load Address: 00000000

Entry Point: 00000000

Verifying Checksum ... OK

Uncompressing Kernel Image ... OK

Memory BAT mapping: BAT2=128Mb, BAT3=0Mb, residual: 0Mb

Linux version 2.4.24-pre2 (satyam@pmcserver) (gcc version 3.2.2 20030217
(Yellow Dog Linux 3.0 3.2.2-2a_1)) #17 Mon Oct 10 15:41:43 IST 2005

On node 0 totalpages: 32768

zone(0): 32768 pages.

zone(1): 0 pages.

zone(2): 0 pages.

Kernel command line: console=ttyS0,115200 root=1f00

Warning: real time clock seems stuck!

Calibrating delay loop... 131.89 BogoMIPS

Memory: 128148k available (948k kernel code, 368k data, 56k init, 0k
highmem)

Dentry cache hash table entries: 16384 (order: 5, 131072 bytes)

Inode cache hash table entries: 8192 (order: 4, 65536 bytes)

Mount cache hash table entries: 512 (order: 0, 4096 bytes)

Buffer cache hash table entries: 8192 (order: 3, 32768 bytes)

Page-cache hash table entries: 32768 (order: 5, 131072 bytes)

POSIX conformance testing by UNIFIX

Linux NET4.0 for Linux 2.4

Based upon Swansea University Computer Society NET3.039

Initializing RT netlink socket

Starting kswapd

JFFS2 version 2.1. (C) 2001 Red Hat, Inc., designed by Axis Communications
AB.

Inside Chr_dev_init

CPM UART driver version 0.01

ttyS0 on SMC1 at 0x0000, BRG7

ttyS1 on SMC2 at 0x0040, BRG8

ttyS2 on SCC1 at 0x8000, BRG1

ttyS3 on SCC2 at 0x8100, BRG2

pty: 256 Unix98 ptys configured

Pty initialisation is complete

eth0: FCC2 ENET Version 0.4, 00:10:EC:40:30:8C

Inside rd_init

RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize

pmc8260 flash map (size->0x2000000 mem->0xFC000000)

map->buswidth : 2

cfi_cmdset_0001: Erase suspend on write enabled

Using buffer write method

Creating 1 MTD partitions on "pmc8260 flash memory":

0x008c0000-0x00bc0000 : "JFFS2 partition"

NET4: Linux TCP/IP 1.0 for NET4.0

IP Protocols: ICMP, UDP, TCP, IGMP

IP: routing cache hash table of 1024 buckets, 8Kbytes

TCP: Hash tables configured (established 8192 bind 16384)

NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.

*****

VFS:test name = /dev/root

VFS:fs_name = jffs2

VFS:root name = 1f:00

****

jffs2_scan_inode_node(): Data CRC failed on node at 0x0003b1a8: Read
0xcd593a55, calculated 0x95474c25

jffs2_scan_inode_node(): CRC failed on node at 0x002aafc0: Read 0x00000001,
calculated 0x8ea9f6b8

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x002aafc8:
0x10e4 instead

Eep. Child "issue" (ino #127) of dir ino #4 doesn't exist!

VFS:tried fs_name = jffs2 err = 0

VFS: Mounted root (jffs2 filesystem) readonly.

Freeing unused kernel memory: 56k init 4k prep

 init started: BusyBox v0.60.5 (2004.11.09-16:07+0000) multi-call
binarymount: Mounting /dev/ram0 on /tmp failed: Invalid argument

Starting networking: done.

Starting udhcp Client: Jan 1 00:00:02 insmod: insmod: net-pf-17: no module
by that name found done.

Starting thttpd: done.

Starting OpenSSH: done.

Starting SNMP Agent: done.

jffs2_read_inode() on nonexistent ino 127

(none) login: root

Password:

Jan 1 00:00:09 login[61]: root login on `ttyS0'

BusyBox v0.60.5 (2004.11.09-16:07+0000) Built-in shell (ash)

Enter 'help' for a list of built-in commands.

# ifconfig eth0 down

# ifconfig eth0 172.19.56.218 <http://172.19.56.218>

# ifconfig eth0 up

# ifconfig

eth0 Link encap:Ethernet HWaddr 00:10:EC:40:30:8C

inet addr:172.19.56.218 <http://172.19.56.218>
Bcast:172.19.255.255<http://172.19.255.255>Mask:
255.255.0.0 <http://255.255.0.0>

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 iB) TX bytes:0 (0.0 iB)

Base address:0x8500

lo Link encap:Local Loopback

inet addr:127.0.0.1 <http://127.0.0.1> Mask:255.0.0.0 <http://255.0.0.0>

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:0 (0.0 iB) TX bytes:0 (0.0 iB)

# ping 127.0.0.1 <http://127.0.0.1>

PING 127.0.0.1 <http://127.0.0.1> (127.0.0.1 <http://127.0.0.1>): 56 data
bytes

64 bytes from 127.0.0.1 <http://127.0.0.1>: icmp_seq=0 ttl=64 time=0.6 ms

64 bytes from 127.0.0.1 <http://127.0.0.1>: icmp_seq=1 ttl=64 time=0.2 ms

64 bytes from 127.0.0.1 <http://127.0.0.1>: icmp_seq=2 ttl=64 time=0.2 ms

64 bytes from 127.0.0.1 <http://127.0.0.1>: icmp_seq=3 ttl=64 time=0.2 ms

64 bytes from 127.0.0.1 <http://127.0.0.1>: icmp_seq=4 ttl=64 time=0.2 ms

--- 127.0.0.1 <http://127.0.0.1> ping statistics ---

5 packets transmitted, 5 packets received, 0% packet loss

round-trip min/avg/max = 0.2/0.2/0.6 ms

#

# ping 172.19.59.101 <http://172.19.59.101>

PING 172.19.59.101 <http://172.19.59.101>
(172.19.59.101<http://172.19.59.101>):
56 data bytes

--- 172.19.59.101 <http://172.19.59.101> ping statistics ---

6 packets transmitted, 0 packets received, 100% packet loss
*******************************************************************************************************
Regards,
Apoorv Sangal.

 On 10/10/05, Mark Chambers <markc@mail.com> wrote:
>
>    Hi
> Thanks for the inputs... As per your suggestion I commented
>  { mk_mii_write(MII_REG_CR, 0x1200), NULL }, /* autonegotiate */
> but it doesn't make any diffrence, still the ping doesn't worked.
>  At Boot loader level (u-boot) Ping works fine,
>   I think you need to provide more information, because there are many
> things
> that could be wrong. Attach the output of your console from the boot
> sequence,
> and include the output of an ifconfig command if you can.
>  Mark Chambers
>
>

[-- Attachment #2: Type: text/html, Size: 8497 bytes --]

Re: Problem Regarding Ping in Linux kernel version 2.4.24

[Mark Chambers]

Hi,
I am sending the output from the console of the boot sequence and ifconfig
command as following.
Please check the same and let me know where i am going wrong.
****************************************************************************
***************************
[snip]

eth0: FCC2 ENET Version 0.4, 00:10:EC:40:30:8C

[snip]
init started: BusyBox v0.60.5 (2004.11.09-16:07+0000) multi-call
binarymount: Mounting /dev/ram0 on /tmp failed: Invalid argument
# ifconfig eth0 down
# ifconfig eth0 172.19.56.218
# ifconfig eth0 up
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:10:EC:40:30:8C
inet addr:172.19.56.218 Bcast:172.19.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 iB) TX bytes:0 (0.0 iB)
Base address:0x8500
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 iB) TX bytes:0 (0.0 iB)
# ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.6 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.2 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.2 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.2 ms
64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.2 ms
--- 127.0.0.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.2/0.2/0.6 ms
#
# ping 172.19.59.101
PING 172.19.59.101 (172.19.59.101): 56 data bytes
--- 172.19.59.101 ping statistics ---
6 packets transmitted, 0 packets received, 100% packet loss
****************************************************************************
***************************
Regards,
Apoorv Sangal.


It appears you have correctly assigned MAC and IP addresses.  The problem
does appear to be at
the hardware level, because the ethernet interface is not doing anything at
all.  My guess would be
that the driver is not configured for the correct pins.  You mentioned that
you are using custom hardware,
so look, probably in arch/ppc/8260_io/fcc_enet.c and make sure you have it
configured for Tx and
Rx clock coming in on the right pins, and also check that you are configured
for the correct PHY
interrupt.

Good luck,
Mark Chambers

Re: MPC8555 USB host support

[Kylo Ginsberg]

Stefan,

I asked a similar question a few months back and found the comments
instructive.  Google for a thread started with this subject: "MPC885 -
USB HCI drivers".

Kylo

On 10/10/05, Stefan Roese <sr@denx.de> wrote:
> I am wondering, if the USB host controller of the MPC8555 is supported at=
 all
> right now. The manual states, that it is similar to, but not fully OHCI o=
r
> UHCI compatible. Any infos about this?
>
> Best regards,
> Stefan
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>

Re: MPC8555 USB host support

[Stefan Roese]

On Tuesday 11 October 2005 22:29, Kylo Ginsberg wrote:
> I asked a similar question a few months back and found the comments
> instructive.  Google for a thread started with this subject: "MPC885 -
> USB HCI drivers".

Thanks for the hint. This brings me back to the "MPC885 - USB HCI drivers" 
thread.

Pantelis, you mentioned an existing (and working ;-)) linux 2.4 USB HCI driver 
for 8xx and 82xx. Did you find the time to clean the driver up? Perhaps, I 
could be your "vict^H^H^Holunteer", to port it to 2.6.

Best regards,
Stefan

Re: MPC8555 USB host support

[Pantelis Antoniou]

Stefan Roese wrote:
> On Tuesday 11 October 2005 22:29, Kylo Ginsberg wrote:
> 
>>I asked a similar question a few months back and found the comments
>>instructive.  Google for a thread started with this subject: "MPC885 -
>>USB HCI drivers".
> 
> 
> Thanks for the hint. This brings me back to the "MPC885 - USB HCI drivers" 
> thread.
> 
> Pantelis, you mentioned an existing (and working ;-)) linux 2.4 USB HCI driver 
> for 8xx and 82xx. Did you find the time to clean the driver up? Perhaps, I 
> could be your "vict^H^H^Holunteer", to port it to 2.6.
> 
> Best regards,
> Stefan
> 
> 

Sure, I can always use a "vict^Wvolunteer" :)

Regards

Pantelis

Re: MPC8555 USB host support

[Mike Rapoport]

Stefan Roese wrote:

>Pantelis, you mentioned an existing (and working ;-)) linux 2.4 USB HCI driver 
>for 8xx and 82xx. Did you find the time to clean the driver up? Perhaps, I 
>could be your "vict^H^H^Holunteer", to port it to 2.6.
>

Stefan,
I don't know if Pantelis found a volo^H^H^Hictim, but I've made some 
porting of the USB HCI driver for
82xx (I afraid 8xx support was broken during the port). But the code is 
*very* ugly and still buggy.

-- 
Sincerely yours,
Mike Rapoport

Re: MPC8555 USB host support

[Stefan Roese]

Mike,

On Wednesday 12 October 2005 09:11, Mike Rapoport wrote:
> I don't know if Pantelis found a volo^H^H^Hictim, but I've made some
> porting of the USB HCI driver for
> 82xx (I afraid 8xx support was broken during the port). But the code is
> *very* ugly and still buggy.

I am currently collecting information about the porting effort, and your "ugly 
and buggy" driver would be very helpful. So, please send me your version as 
well. Thanks.
 
Best regards,
Stefan

Re: MPC8555 USB host support

[Alex Zeffertt]

On Wed, 12 Oct 2005 09:27:56 +0200
Stefan Roese <sr@denx.de> wrote:

> Mike,
> 
> On Wednesday 12 October 2005 09:11, Mike Rapoport wrote:
> > I don't know if Pantelis found a volo^H^H^Hictim, but I've made
> > some porting of the USB HCI driver for
> > 82xx (I afraid 8xx support was broken during the port). But the
> > code is*very* ugly and still buggy.
> 
> I am currently collecting information about the porting effort, and
> your "ugly and buggy" driver would be very helpful. So, please send
> me your version as well. Thanks.
>  

Yes me too please.  Also Russell McGuire was asking earlier about
this. Maybe the best thing to do would be to create a sourceforge
project and post the latest patches there.  I have an 8272ads board
and I'd be happy to test it out and provide feedback.

Regards,

Alex

Re: MPC8555 USB host support

[Mike Rapoport]

Alex,

>this. Maybe the best thing to do would be to create a sourceforge
>project and post the latest patches there.  I have an 8272ads board
>  
>
Following your advice I've created a sourceforge project for the USB 
drivers for mpc82xx. For now I've posted there only 2.6 version. As for 
driver for 2.4, it would be better if it'll be posted by someone who's 
actually working with USB in Linux 2.4.

>and I'd be happy to test it out and provide feedback.
>
>Regards,
>
>Alex
>
>
>
>  
>


-- 
Sincerely yours,
Mike Rapoport

Re: MPC8555 USB host support

[Mike Rapoport]

Hans Schillstrom wrote:

>Hi Mike
>I'm working with a 8270 board and 2.6.12 kernel and searching for USB
>drivers.
>
>Could you help me finding the files ?
>  
>
I've opened a project on the SourceForge, 
http://cpm2usb.sourceforge.net. The file containing patch against 
2.6.12.3 can be downloaded at http://sourceforge.net/projects/cpm2usb.

>I can help you with the testing.
>What status do they have right now ?
>  
>
The driver was developed on MPC8272ADS, but should go as well on 8270 
since they have the same USB host controller AFAIK.
Currently, as far as I tested it works fine with full-speed single 
device attached through hub, but fails is there are transfers from/to 
several devices simultaneously.
As for the code itself, it's far from being perfect.

>Regards 
>Hans
>  
>


-- 
Sincerely yours,
Mike Rapoport

Re: MPC8555 USB host support

[Alexandre BASTOS]

Mike,


> I've opened a project on the SourceForge,
> http://cpm2usb.sourceforge.net. The file containing patch against
> 2.6.12.3 can be downloaded at http://sourceforge.net/projects/cpm2usb.
>
> The driver was developed on MPC8272ADS, but should go as well on 8270
> since they have the same USB host controller AFAIK.
> Currently, as far as I tested it works fine with full-speed single
> device attached through hub, but fails is there are transfers from/to
> several devices simultaneously.
> As for the code itself, it's far from being perfect.


I have been testing your cpm2usb driver from sourceforge on my
MPC8272ADS and I couldn't get a usb 2.0 pendrive working.

usbcore tries to identify the device with both schemes, old and
new, but the hcd returns always a timeout. The output from console:

# modprobe usbcore
usbcore: registered new driver usbfs
usbcore: registered new driver hub

# modprobe m82xx-hcd
=> driver mpc82xx-hcd, 2005
mpc82xx-hcd mpc82xx-hcd.3: PQ2 intergrated USB controller v0.1
mpc82xx-hcd mpc82xx-hcd.3: new USB bus registered, assigned bus number 1
usb usb1: Product: PQ2 intergrated USB controller v0.1
usb usb1: Manufacturer: Linux 2.6.12 mpc82xx-hcd
usb usb1: SerialNumber: mpc82xx-hcd.3
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
PQ2USB: debug file creation

[... After pendrive insertion]

usb 1-1: new full speed USB device using mpc82xx-hcd and address 2
usb 1-1: device descriptor read/64, error -110
usb 1-1: device descriptor read/64, error -110
usb 1-1: new full speed USB device using mpc82xx-hcd and address 3
usb 1-1: device descriptor read/64, error -110
usb 1-1: device descriptor read/64, error -110
usb 1-1: new full speed USB device using mpc82xx-hcd and address 4
usb 1-1: device not accepting address 4, error -110
usb 1-1: new full speed USB device using mpc82xx-hcd and address 5
usb 1-1: device not accepting address 5, error -110

To compile the driver as a module, I made only a change in "tx_err"
function from m82xx-hcd.c, which shouldn't be affecting.
I have also commented out the re-definition of BCSR_ADDR, which is
already defined to f4500000 in pq2ads.h

--- m82xx-hcd.c.orig    2005-11-15 12:05:40.547987056 +0100
+++ m82xx-hcd.c 2005-11-14 18:15:13.000000000 +0100
@@ -98,7 +98,7 @@
        hp->usb_clock = USB_CLOCK_PC24_CLK8;

        {
-#define BCSR_ADDR              ((uint)0xf8000000)
+//#define BCSR_ADDR            ((uint)0xf8000000)
        volatile uint* bcsr_usb = (volatile uint*)(BCSR_ADDR +
                                                   BCSR_USB_OFFSET);

@@ -281,7 +281,9 @@
 static void tx_err(struct m8xxhci_private *hp, int ber)
 {
        volatile usbregs_t *usbregs = hp->usbregs;
-       volatile cpm_cpm2_t *cp = cpmp;
+       //volatile cpm_cpm2_t *cp = cpmp;
+       volatile cpm2_map_t *immap = (volatile cpm2_map_t *)CPM_MAP_ADDR;
+       volatile cpm_cpm2_t *cp = &immap->im_cpm;

        if ( hp->active_qe )
                hp->stats.txe[hp->active_qe->qtype]++;

So, any idea which could be happening? I have little knowledge about usb
so I am quite lost.


Thanks.

Alex BASTOS

Re: MPC8555 USB host support

[Kumar Gala]

Any reason not to get this driver into the kernel main line?

- kumar

On Nov 15, 2005, at 12:59 AM, Mike Rapoport wrote:

> Hans Schillstrom wrote:
>
>> Hi Mike
>> I'm working with a 8270 board and 2.6.12 kernel and searching for USB
>> drivers.
>>
>> Could you help me finding the files ?
>>
> I've opened a project on the SourceForge, http:// 
> cpm2usb.sourceforge.net. The file containing patch against 2.6.12.3  
> can be downloaded at http://sourceforge.net/projects/cpm2usb.
>
>> I can help you with the testing.
>> What status do they have right now ?
>>
> The driver was developed on MPC8272ADS, but should go as well on  
> 8270 since they have the same USB host controller AFAIK.
> Currently, as far as I tested it works fine with full-speed single  
> device attached through hub, but fails is there are transfers from/ 
> to several devices simultaneously.
> As for the code itself, it's far from being perfect.
>
>> Regards Hans
>>
>
>
> -- 
> Sincerely yours,
> Mike Rapoport
>
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

Re: MPC8555 USB host support

[Mike Rapoport]

Kumar Gala wrote:

> Any reason not to get this driver into the kernel main line?

In my opinion there is a lot of work to be done to get the driver 
upstream. If you'd like to I can clean it up and post a patch here.

>
> - kumar
>
> On Nov 15, 2005, at 12:59 AM, Mike Rapoport wrote:
>
>


-- 
Sincerely yours,
Mike Rapoport

Re: MPC8555 USB host support

[Vitaly Bordug]

Kumar Gala wrote:
> Any reason not to get this driver into the kernel main line?
I guess because this device is known to work in some specific instance, 
but bot generic one. The best we can do is to consolidate our efforts to 
make it more usable or state that it is impossible.

> 
> - kumar
> 
> On Nov 15, 2005, at 12:59 AM, Mike Rapoport wrote:
> 
>> Hans Schillstrom wrote:
>>
>>> Hi Mike
>>> I'm working with a 8270 board and 2.6.12 kernel and searching for USB
>>> drivers.
>>>
>>> Could you help me finding the files ?
>>>
>> I've opened a project on the SourceForge, 
>> http://cpm2usb.sourceforge.net. The file containing patch against 
>> 2.6.12.3 can be downloaded at http://sourceforge.net/projects/cpm2usb.
>>
>>> I can help you with the testing.
>>> What status do they have right now ?
>>>
>> The driver was developed on MPC8272ADS, but should go as well on 8270 
>> since they have the same USB host controller AFAIK.
>> Currently, as far as I tested it works fine with full-speed single 
>> device attached through hub, but fails is there are transfers from/to 
>> several devices simultaneously.
>> As for the code itself, it's far from being perfect.
>>
>>> Regards Hans
>>>
>>
>>
>> --Sincerely yours,
>> Mike Rapoport
>>
>>
>> _______________________________________________
>> Linuxppc-embedded mailing list
>> Linuxppc-embedded@ozlabs.org
>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 
> 


-- 
Sincerely,
Vitaly

Re: MPC8555 USB host support

[Kumar Gala]

Hmm, we should understand what caveats it has and still look at  
getting it into mainline.

Also, are you aware of Freescale's driver for this?

- kumar

On Nov 15, 2005, at 9:40 AM, Vitaly Bordug wrote:

> Kumar Gala wrote:
>> Any reason not to get this driver into the kernel main line?
> I guess because this device is known to work in some specific  
> instance, but bot generic one. The best we can do is to consolidate  
> our efforts to make it more usable or state that it is impossible.
>
>> - kumar
>> On Nov 15, 2005, at 12:59 AM, Mike Rapoport wrote:
>>> Hans Schillstrom wrote:
>>>
>>>> Hi Mike
>>>> I'm working with a 8270 board and 2.6.12 kernel and searching  
>>>> for USB
>>>> drivers.
>>>>
>>>> Could you help me finding the files ?
>>>>
>>> I've opened a project on the SourceForge, http:// 
>>> cpm2usb.sourceforge.net. The file containing patch against  
>>> 2.6.12.3 can be downloaded at http://sourceforge.net/projects/ 
>>> cpm2usb.
>>>
>>>> I can help you with the testing.
>>>> What status do they have right now ?
>>>>
>>> The driver was developed on MPC8272ADS, but should go as well on  
>>> 8270 since they have the same USB host controller AFAIK.
>>> Currently, as far as I tested it works fine with full-speed  
>>> single device attached through hub, but fails is there are  
>>> transfers from/to several devices simultaneously.
>>> As for the code itself, it's far from being perfect.
>>>
>>>> Regards Hans
>>>>
>>>
>>>
>>> --Sincerely yours,
>>> Mike Rapoport
>>>
>>>
>>> _______________________________________________
>>> Linuxppc-embedded mailing list
>>> Linuxppc-embedded@ozlabs.org
>>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>> _______________________________________________
>> Linuxppc-embedded mailing list
>> Linuxppc-embedded@ozlabs.org
>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
> -- 
> Sincerely,
> Vitaly

Re: MPC8555 USB host support

[Vitaly Bordug]

Kumar Gala wrote:
> Hmm, we should understand what caveats it has and still look at getting 
> it into mainline.
> 
I also have a bunch of patches for gregkh, supporting serial function, but they need 
nontrivial cleanup I do not have time currently for. So I think I grab this one together 
with my stuff when I head for it.

> Also, are you aware of Freescale's driver for this?
> 
I used to try arabella one (came with MW bsp) but that version does not work with 8272.
If there are something usable, it will be interesting to look at.

> - kumar
> 
> On Nov 15, 2005, at 9:40 AM, Vitaly Bordug wrote:
> 
>> Kumar Gala wrote:
>>> Any reason not to get this driver into the kernel main line?
>> I guess because this device is known to work in some specific 
>> instance, but bot generic one. The best we can do is to consolidate 
>> our efforts to make it more usable or state that it is impossible.
>>
>>> - kumar
>>> On Nov 15, 2005, at 12:59 AM, Mike Rapoport wrote:
>>>> Hans Schillstrom wrote:
>>>>
>>>>> Hi Mike
>>>>> I'm working with a 8270 board and 2.6.12 kernel and searching for USB
>>>>> drivers.
>>>>>
>>>>> Could you help me finding the files ?
>>>>>
>>>> I've opened a project on the SourceForge, 
>>>> http://cpm2usb.sourceforge.net. The file containing patch against 
>>>> 2.6.12.3 can be downloaded at http://sourceforge.net/projects/cpm2usb.
>>>>
>>>>> I can help you with the testing.
>>>>> What status do they have right now ?
>>>>>
>>>> The driver was developed on MPC8272ADS, but should go as well on 
>>>> 8270 since they have the same USB host controller AFAIK.
>>>> Currently, as far as I tested it works fine with full-speed single 
>>>> device attached through hub, but fails is there are transfers 
>>>> from/to several devices simultaneously.
>>>> As for the code itself, it's far from being perfect.
>>>>
>>>>> Regards Hans
>>>>>
>>>>
>>>>
>>>> --Sincerely yours,
>>>> Mike Rapoport
>>>>
>>>>
>>>> _______________________________________________
>>>> Linuxppc-embedded mailing list
>>>> Linuxppc-embedded@ozlabs.org
>>>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>> _______________________________________________
>>> Linuxppc-embedded mailing list
>>> Linuxppc-embedded@ozlabs.org
>>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>
>>
>> --Sincerely,
>> Vitaly
> 
> 


-- 
Sincerely,
Vitaly

Re: MPC8555 USB host support

[Yuli Barcohen]

>>>>> Vitaly Bordug writes:

...

    Vitaly> I also have a bunch of patches for gregkh, supporting serial
    Vitaly> function, but they need nontrivial cleanup I do not have
    Vitaly> time currently for. So I think I grab this one together with
    Vitaly> my stuff when I head for it.

    Kumar> Also, are you aware of Freescale's driver for this?

    Vitaly> I used to try arabella one (came with MW bsp) but that
    Vitaly> version does not work with 8272.

If so, it's a very old version. The driver works with any MPC82xx (and
MPC885, BTW). Also, please remember that many Freescale ADS boards have
hardware problems (depending on the board's revision).

    Vitaly> If there are something usable, it will be interesting to
    Vitaly> look at.

...

-- 
========================================================================
 Yuli Barcohen       | Phone +972-9-765-1788 |  Software Project Leader
 yuli@arabellasw.com | Fax   +972-9-765-7494 | Arabella Software, Israel
========================================================================

Re: MPC8555 8280/8270 USB host support

[Hans Schillstrom]

[-- Attachment #1: Type: text/plain, Size: 1475 bytes --]

Hi Mike
I've made some modifications due to the difference between mpc8272 and
mpc8270. MPC8272 use SCC3 and MPC8270 use SCC4.
Added some more clock configuration options ...

I think the changes are quite generic.

The driver seems to work with a 2.6.13 kernel.
Only some basic tests is performed with
- serial ftdi_sio to ports ttyUSB0 & ttyUSB1
- storage i.e. some kind of "no name" usb-memory 
- 3 1/4 floppy drive
- Nokia hub.


Don't you think u-boot should take care of clock setup
i.e. as much as possible of all board dependent stuff ?


Regards 
Hans Schillstrom

On Tue, 2005-11-15 at 07:59, Mike Rapoport wrote:
> Hans Schillstrom wrote:
> 
> >Hi Mike
> >I'm working with a 8270 board and 2.6.12 kernel and searching for USB
> >drivers.
> >
> >Could you help me finding the files ?
> >  
> >
> I've opened a project on the SourceForge, 
> http://cpm2usb.sourceforge.net. The file containing patch against 
> 2.6.12.3 can be downloaded at http://sourceforge.net/projects/cpm2usb.
> 
> >I can help you with the testing.
> >What status do they have right now ?
> >  
> >
> The driver was developed on MPC8272ADS, but should go as well on 8270 
> since they have the same USB host controller AFAIK.
> Currently, as far as I tested it works fine with full-speed single 
> device attached through hub, but fails is there are transfers from/to 
> several devices simultaneously.
> As for the code itself, it's far from being perfect.
> 
> >Regards 
> >Hans
> >  
> >
> 

[-- Attachment #2: m8270usb.patch --]
[-- Type: text/x-patch, Size: 6861 bytes --]

diff -Nruw linux-2.6.13.2/drivers/usb/host/m82xx-hcd.c linux-2.6-dev/drivers/usb/host/m82xx-hcd.c
--- linux-2.6.13.2/drivers/usb/host/m82xx-hcd.c	2005-12-01 10:58:55.000000000 +0100
+++ linux-2.6-dev/drivers/usb/host/m82xx-hcd.c	2005-12-01 12:59:27.000000000 +0100
@@ -12,6 +12,9 @@
  * George Panageas <gpana@intracom.gr>
  * Pantelis Antoniou <panto@intracom.gr>
  *
+ * Fixes for MPC8270/80 & adaptions to powervave technologies rcb8270 board.
+ *  Hans Schillstrom <hans.schillstrom@pwav.com>
+ *
  * designed for the EmbeddedPlanet RPX lite board
  * (C) Copyright 2000 Embedded Planet
  * http://www.embeddedplanet.com
@@ -110,6 +113,15 @@

 	*bcsr_usb |= BCSR_USB_POWER;
 	}
+#elif defined(CONFIG_RCB8270)
+        hp->usb_clock = USB_CLOCK_PC25_CLK7;
+        {
+          volatile cpm2_map_t *immap = (volatile cpm2_map_t *)CPM_MAP_ADDR;
+          volatile iop_cpm2_t *io = &immap->im_ioport;
+
+          io->iop_pdata &= ~(1 << (31 - 2));  // Turn on power tu usb driver
+          udelay(1000);
+        }
 #endif
 	return 0;
 }
@@ -167,26 +179,39 @@
 	volatile cpmux_t *cm = &immap->im_cpmux;

 	switch (usb_clock) {
+                case USB_CLOCK_PC27_CLK5:
+                        io->iop_pdirc &= ~PC_CLK5_48MHz;
+                        io->iop_psorc &= ~PC_CLK5_48MHz;
+                        io->iop_pparc |=  PC_CLK5_48MHz;
+                        cm->cmx_scr &= ~USB_CMX_SCR_MASK;
+                        cm->cmx_scr |=  USB_CMX_CLK5;
+                        break;
 		case USB_CLOCK_PC26_CLK6:
 			io->iop_pdirc &= ~PC_CLK6_48MHz;
 			io->iop_psorc &= ~PC_CLK6_48MHz;
 			io->iop_pparc |=  PC_CLK6_48MHz;
-			cm->cmx_scr &= ~0x0000ff00;
-			cm->cmx_scr |=  0x00003f00;
+			cm->cmx_scr &= ~USB_CMX_SCR_MASK;
+			cm->cmx_scr |=  USB_CMX_CLK6;
+			break;
+                case USB_CLOCK_PC25_CLK7:
+                        io->iop_pdirc &= ~PC_CLK7_48MHz;    // Input mode
+                        io->iop_psorc &= ~PC_CLK7_48MHz;    // special option
+                        io->iop_pparc |=  PC_CLK7_48MHz;    // Dedicated port
+                        cm->cmx_scr &= ~USB_CMX_SCR_MASK;
+                        cm->cmx_scr |=  USB_CMX_CLK7;
 			break;
 		case USB_CLOCK_PC24_CLK8:
 			io->iop_pdirc &= ~PC_CLK8_48MHz;
 			io->iop_psorc &= ~PC_CLK8_48MHz;
 			io->iop_pparc |=  PC_CLK8_48MHz;
-			cm->cmx_scr &= ~0x0000ff00;
-			cm->cmx_scr |=  0x00003f00;
+			cm->cmx_scr &= ~USB_CMX_SCR_MASK;
+			cm->cmx_scr |=  USB_CMX_CLK8;
 			break;

 		default:
 			printk(KERN_ERR "m8xxhci: invalid usb_clock value %d!\n", usb_clock);
 			return -1;
 	}
-
 	return 0;
 }

@@ -317,13 +342,21 @@
 #define USB_MODE_PIN	((uint)(1 << (31 - 0)))
 #define USB_SPEED_PIN	((uint)(1 << (31 - 23)))
 #define USB_SUSPEND_PIN ((uint)(1 << (31 - 29)))
-
-
 	io->iop_pdirc |= (USB_MODE_PIN | USB_SPEED_PIN | USB_SUSPEND_PIN);
 	io->iop_pparc &= ~(USB_MODE_PIN | USB_SPEED_PIN | USB_SUSPEND_PIN);
 	io->iop_pdatc |= (USB_MODE_PIN | USB_SPEED_PIN);
 	io->iop_podrc |= USB_MODE_PIN;
 	io->iop_pdatc &= ~(USB_SUSPEND_PIN);
+
+#elif defined(CONFIG_RCB8270)
+
+#define USB_MODE_PIN	((uint)(1 << (31 - 0)))
+#define USB_SPEED_PIN	((uint)(1 << (31 - 5)))
+
+	io->iop_pdirc |= (USB_MODE_PIN | USB_SPEED_PIN );
+	io->iop_pparc &= ~(USB_MODE_PIN | USB_SPEED_PIN );
+	io->iop_pdatc |= (USB_MODE_PIN | USB_SPEED_PIN);
+	io->iop_podrc |= USB_MODE_PIN;
 #endif

 	msleep(10);
diff -Nruw linux-2.6.13.2/drivers/usb/host/m82xx-hcd.h linux-2.6-dev/drivers/usb/host/m82xx-hcd.h
--- linux-2.6.13.2/drivers/usb/host/m82xx-hcd.h	2005-12-01 10:58:55.000000000 +0100
+++ linux-2.6-dev/drivers/usb/host/m82xx-hcd.h	2005-11-22 11:07:44.000000000 +0100
@@ -16,6 +16,9 @@
  * (C) Copyright 2000 Embedded Planet
  * http://www.embeddedplanet.com
  *
+ * Fixes for MPC8270/80
+ *  Hans Schillstrom <hans.schillstrom@pwav.com>
+ *
  */

 #ifndef M82XXHCI_H
@@ -42,9 +45,21 @@
 #endif

 #ifdef CONFIG_CPM2
+
+#ifdef CONFIG_RCB8270
+# ifndef CONFIG_MPC8270
+#  define CONFIG_MPC8270 1
+# endif
+#endif
+
+#if defined(CONFIG_MPC8270) || defined(CONFIG_MPC8280)
+#define USB_SCC_IDX	3	/* SCC4 */
+#define CPMVEC_USB	(CPM_IRQ_OFFSET + CPMVEC_SCC4)
+#else
 #define USB_SCC_IDX	2	/* SCC3 */
 #define CPMVEC_USB	(CPM_IRQ_OFFSET + CPMVEC_SCC3)
 #endif
+#endif

 #define BD_USB_TC       ((ushort)0x0400)        /* transmit crc after last */
 #define BD_USB_CNF      ((ushort)0x0200)        /* wait for handshake */
@@ -238,6 +253,41 @@
 #endif

 #ifdef CONFIG_CPM2
+/* Clock source setting */
+#define USB_CMX_SCR_MASK  ((uint)(0xff000000 >> (USB_SCC_IDX<<3)))
+#define USB_CMX_CLK5      ((uint)((CMXSCR_RS1CS_CLK11 | CMXSCR_TS1CS_CLK11) >> (USB_SCC_IDX<<3)))
+#define USB_CMX_CLK6      ((uint)((CMXSCR_RS1CS_CLK12 | CMXSCR_TS1CS_CLK12) >> (USB_SCC_IDX<<3)))
+#define USB_CMX_CLK7      ((uint)((CMXSCR_RS1CS_CLK3 | CMXSCR_TS1CS_CLK3) >> (USB_SCC_IDX<<3)))
+#define USB_CMX_CLK8      ((uint)((CMXSCR_RS1CS_CLK4 | CMXSCR_TS1CS_CLK4) >> (USB_SCC_IDX<<3)))
+
+#define PC_CLK5_48MHz	((uint)(1 << (31 - 27)))
+#define PC_CLK6_48MHz	((uint)(1 << (31 - 26)))
+#define PC_CLK7_48MHz	((uint)(1 << (31 - 25)))
+#define PC_CLK8_48MHz	((uint)(1 << (31 - 24)))
+
+#if defined(CONFIG_MPC8270) || defined(CONFIG_MPC8280)
+
+/* bits in parallel i/o port registers that have to be cleared to  */
+/* configure the pins for SCC4 USB use.                            */
+                                                        /* sor dir */
+                                                        /* --- --- */
+#define PD_USB_RXD      ((uint)(1 << (31 - 22)))	/*  0   0  */
+#define PD_USB_TN       ((uint)(1 << (31 - 21)))	/*  0   1  */
+#define PD_USB_TP       ((uint)(1 << (31 - 20)))	/*  0   1  */
+
+#define PD_MSK		(PD_USB_RXD | PD_USB_TN | PD_USB_TP)
+#define PD_DIR0		PD_USB_RXD
+#define PD_DIR1		(PD_USB_TN | PD_USB_TP)
+
+#define PC_USB_OE	((uint)(1 << (31 - 20)))	/*  0   1  */
+#define PC_USB_RP	((uint)(1 << (31 - 9))) 	/*  0   0  */
+#define PC_USB_RN	((uint)(1 << (31 - 8))) 	/*  0   0  */
+
+#define PC_MSK		(PC_USB_OE | PC_USB_RP | PC_USB_RN)
+#define PC_DIR0		(PC_USB_RP | PC_USB_RN)
+#define PC_DIR1		PC_USB_OE
+
+#else

 /* bits in parallel i/o port registers that have to be cleared to  */
 /* configure the pins for SCC1 USB use.                            */
@@ -259,8 +309,7 @@
 #define PC_DIR0		(PC_USB_RP | PC_USB_RN)
 #define PC_DIR1		PC_USB_OE

-#define PC_CLK6_48MHz	((uint)(1 << (31 - 26)))	/*  0   0  */
-#define PC_CLK8_48MHz	((uint)(1 << (31 - 24)))	/*  0   0  */
+#endif

 #endif

@@ -409,7 +458,9 @@
 	USB_CLOCK_PA6_CLK2,
 	USB_CLOCK_BRG3,
 	USB_CLOCK_BRG4,
+        USB_CLOCK_PC27_CLK5,
 	USB_CLOCK_PC26_CLK6,
+        USB_CLOCK_PC25_CLK7,
 	USB_CLOCK_PC24_CLK8,
 	USB_CLOCK_CNT,
 };

Re: MPC8555 8280/8270 USB host support

[Mike Rapoport]

Hans Schillstrom wrote:

>Hi Mike
>I've made some modifications due to the difference between mpc8272 and
>mpc8270. MPC8272 use SCC3 and MPC8270 use SCC4.
>Added some more clock configuration options ...
>  
>
Thanks a lot.
I've added your patch as is to the SF page.

>
>Don't you think u-boot should take care of clock setup
>i.e. as much as possible of all board dependent stuff ?
>  
>
I think you're right, but then it was easier to make all these setups in 
the driver itself.

>
>Regards 
>Hans Schillstrom
>
>  
>

-- 
Sincerely yours,
Mike Rapoport

Re: MPC8555 8280/8270 USB host support

[Wolfgang Denk]

In message <1133439981.8518.237.camel@hawk.pwav.net> you wrote:
> 
> Don't you think u-boot should take care of clock setup
> i.e. as much as possible of all board dependent stuff ?

No, it should not. A river should not make any assumptions about  the
state of the hardware, but initialize everything it needs for correct
operation itself.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Save yourself!  Reboot in 5 seconds!

Re: MPC8555 8280/8270 USB host support

[Nathael PAJANI]

Hi

 >
 >>
 >>Don't you think u-boot should take care of clock setup
 >>i.e. as much as possible of all board dependent stuff ?
 >>
 >>
 >I think you're right, but then it was easier to make all these setups 
 >in the driver itself.
 >

If u-boot is the boot loader of your board (the stuff running on it 
--before-- we see this:

loaded at:     00400000 005153B4
board data at: 00513130 00513334
relocated to:  00405090 00405294
zimage at:     00405A85 00512099
avail ram:     00516000 08000000

Linux/PPC load: rw console=ttyS0 root=/dev/nfs ip=on

Uncompressing Linux...done)


Then I would say NO




If u-boot is this exact stuff (the files in arch/ppc/boot/simple/... 
misc-embedded.c for example)

then, yes, this is somehow better.
But (tell me if I'm wrong) this is not really Linux code, and this 
should be done by Linux.


What I think should be good also is the platform files 
(arch/ppc/platforms/....) for this is the place where all the board 
dependant stuff stays.




Maybe I'm completely mistaken.
Feel free to tell me (and explain please !)

Have fun.

Re: MPC8555 8280/8270 USB host support

[Wolfgang Denk]

In message <438F198F.9020606@cpe.fr> you wrote:
> 
> If u-boot is the boot loader of your board (the stuff running on it 
> --before-- we see this:
> 
> loaded at:     00400000 005153B4
> board data at: 00513130 00513334
> relocated to:  00405090 00405294
> zimage at:     00405A85 00512099
> avail ram:     00516000 08000000

If U-Boot is your boot load, *and* you see this, than you  made  some
serious  mistake.  U-Boot  is  supposed  to boot the "uImage" images,
which do not issue such messages.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
The shortest unit of time in the multiverse is the News York  Second,
defined  as  the  period  of  time between the traffic lights turning
green and the cab behind you honking.
                                - Terry Pratchett, _Lords and Ladies_