* Re: [PATCH 2/3] powerpc: Instrument Hypervisor Calls: add wrappers
From: Mike Kravetz @ 2006-06-14 23:52 UTC (permalink / raw)
To: Nathan Lynch
Cc: Bryan Rosenburg, linuxppc-dev, Paul Mackerras, Christopher Yeoh
In-Reply-To: <20060614224040.GH26750@localdomain>
On Wed, Jun 14, 2006 at 05:40:40PM -0500, Nathan Lynch wrote:
> Makes sense... then perhaps the stats shouldn't be exported in per-cpu
> files in sysfs, and the kernel should calculate and report the totals
> to userspace in some other form.
I'm really wondering what would be the best way to make these stats
available to userspace. As mentioned, putting them into sysfs would
violate the one value/one file rule. The use of /proc is discouraged.
debugfs was mentioned, but I have never used it. Noticed that debugfs
was enabled in the default config (at least for pseries). Looks like
that would be the best alternative. Agree?
--
Mike
^ permalink raw reply
* Re: USB flashdrive on Motorola MPC5200 (IceCube) board, linux ke rnel 2.4.20
From: Wolfgang Denk @ 2006-06-14 23:02 UTC (permalink / raw)
To: Furxhi, Orges; +Cc: linuxppc-embedded
In-Reply-To: <162B449665D6D643AD9E1D50FC6F4B1403F16E83@mdcexc05.na.ops.local>
In message <162B449665D6D643AD9E1D50FC6F4B1403F16E83@mdcexc05.na.ops.local> you wrote:
...
> I am using the kernel build using the ELDK 3.1.1 tools and a file system
> which was build using Montavista tools (DevRocket 1.1). Is that a problem???
Don't know. Why don't you try either the ramdisk image or the NFS
root file system that comes included with the ELDK? Both are known to
work fine, and testing should take less than 5 minutes.
> Kernel command line: root=/dev/mtdblock2 rw rootfstype=jffs2
> ip=192.168.0.7:192.
...
How did you create the root file system image, and how did you write
it to flash?
> devfs_register(ttyS): could not append to parent, err: -17
> devfs_register(ttyS): could not append to parent, err: -17
> devfs_register(cua): could not append to parent, err: -17
> devfs_register(cua): could not append to parent, err: -17
This doesn't look so good to me. I recommend to disable devfs in your
kernel configuration.
...
Eventually the kernel does not find the needed /dev/ entries. Make
sure what your root filesystem expects. Does it really use devfs?
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
"Wagner's music is better than it sounds." - Mark Twain
^ permalink raw reply
* Re: [PATCH 2/3] powerpc: Instrument Hypervisor Calls: add wrappers
From: Nathan Lynch @ 2006-06-14 22:40 UTC (permalink / raw)
To: Paul Mackerras; +Cc: Bryan Rosenburg, Christopher Yeoh, linuxppc-dev
In-Reply-To: <17552.36563.460775.131555@cargo.ozlabs.ibm.com>
Paul Mackerras wrote:
> Nathan Lynch writes:
>
> > Without disabling preemption around the mfspr ... update_stats section
> > in these hcall wrappers, you risk updating the stats on the wrong cpu.
>
> I think we are only looking for total counts and times anyway, so it
> doesn't really matter which cpu updates the stats, as long as the time
> gets accounted on some cpu. The use of per-cpu counters is just for
> better cache behaviour.
Makes sense... then perhaps the stats shouldn't be exported in per-cpu
files in sysfs, and the kernel should calculate and report the totals
to userspace in some other form.
^ permalink raw reply
* Re: [PATCH 2/3] powerpc: Instrument Hypervisor Calls: add wrappers
From: Paul Mackerras @ 2006-06-14 22:33 UTC (permalink / raw)
To: Nathan Lynch; +Cc: Bryan Rosenburg, Christopher Yeoh, linuxppc-dev
In-Reply-To: <20060614144230.GE26750@localdomain>
Nathan Lynch writes:
> Without disabling preemption around the mfspr ... update_stats section
> in these hcall wrappers, you risk updating the stats on the wrong cpu.
I think we are only looking for total counts and times anyway, so it
doesn't really matter which cpu updates the stats, as long as the time
gets accounted on some cpu. The use of per-cpu counters is just for
better cache behaviour.
Paul.
^ permalink raw reply
* Re: [OOPS] 2.6.17-rc3 on an mpc8241
From: Johannes Berg @ 2006-06-14 22:27 UTC (permalink / raw)
To: Guennadi Liakhovetski; +Cc: linuxppc-dev
In-Reply-To: <Pine.LNX.4.60.0606150017380.12545@poirot.grange>
[-- Attachment #1: Type: text/plain, Size: 222 bytes --]
On Thu, 2006-06-15 at 00:25 +0200, Guennadi Liakhovetski wrote:
> As I said - already reported and fixed in 2.6.17-rc6:
Ah, I saw that but didn't make the connection. Sorry. Good to know it's
fine now.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]
^ permalink raw reply
* Re: [OOPS] 2.6.17-rc3 on an mpc8241
From: Guennadi Liakhovetski @ 2006-06-14 22:25 UTC (permalink / raw)
To: Johannes Berg; +Cc: linuxppc-dev
In-Reply-To: <1150323066.13958.28.camel@johannes.berg>
On Thu, 15 Jun 2006, Johannes Berg wrote:
> On Thu, 2006-06-15 at 00:08 +0200, Guennadi Liakhovetski wrote:
>
> > Ghm, ok, I know what that was - the very same bug I myself reported
> > earlier in asm-offsets...
>
> in asm-offsets? Are you saying that you know what caused this and I
> shouldn't bother looking at it?
As I said - already reported and fixed in 2.6.17-rc6:
From: Linus Torvalds <>
To: Linux Kernel Mailing List <>
Subject: Linux v2.6.17-rc6
...
Paul Mackerras:
Add CMSPAR to termbits.h for powerpc and alpha
ppc: Fix typo in TI_LOCAL_FLAGS definition
Thanks
Guennadi
---
Guennadi Liakhovetski
^ permalink raw reply
* Re: [OOPS] 2.6.17-rc3 on an mpc8241
From: Johannes Berg @ 2006-06-14 22:11 UTC (permalink / raw)
To: Guennadi Liakhovetski; +Cc: linuxppc-dev
In-Reply-To: <Pine.LNX.4.60.0606150007430.12545@poirot.grange>
[-- Attachment #1: Type: text/plain, Size: 366 bytes --]
On Thu, 2006-06-15 at 00:08 +0200, Guennadi Liakhovetski wrote:
> Ghm, ok, I know what that was - the very same bug I myself reported
> earlier in asm-offsets...
in asm-offsets? Are you saying that you know what caused this and I
shouldn't bother looking at it?
> how do you say it in English - twice in the same
> trap?:-)
No idea :)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]
^ permalink raw reply
* Re: [OOPS] 2.6.17-rc3 on an mpc8241
From: Guennadi Liakhovetski @ 2006-06-14 22:08 UTC (permalink / raw)
To: Johannes Berg; +Cc: linuxppc-dev
In-Reply-To: <Pine.LNX.4.60.0606142300120.12545@poirot.grange>
On Wed, 14 Jun 2006, Guennadi Liakhovetski wrote:
> On Wed, 14 Jun 2006, Johannes Berg wrote:
>
> > On Wed, 2006-06-14 at 22:48 +0200, Guennadi Liakhovetski wrote:
> > > Corrupted stack?...
> >
> > Looks weird.
> > Enable slab debugging? :)
>
> Compiling 2.6.17-rc5... And I don't know how easy it is to reproduce...
> Once I have the kernel ready will try...
Ghm, ok, I know what that was - the very same bug I myself reported
earlier in asm-offsets... how do you say it in English - twice in the same
trap?:-)
Thanks
Guennadi
---
Guennadi Liakhovetski
^ permalink raw reply
* RE: USB flashdrive on Motorola MPC5200 (IceCube) board, linux ke rnel 2.4.20
From: Furxhi, Orges @ 2006-06-14 21:48 UTC (permalink / raw)
To: Wolfgang Denk, Furxhi, Orges, Igor Luri; +Cc: linuxppc-embedded
[-- Attachment #1: Type: text/plain, Size: 7397 bytes --]
Thank you al for your help.
>> I downloaded the kernel you recommended and now I am trying to build a
>>UBoot
>> image that I can load unto flash.
>> I use the following commands:
>> $ make mrproper
>> $ make menuconfig
>> (select arch/ppc/configs/icecube_5200_defconfig file, exit and save)
>> $ make uImage
>Try instead:
> $ make mrproper
> $ make icecube_5200_config
> $ make oldconfig
> $ make dep
> $ make uImage
I was able to build the UBoot image and load it unto my boards flash.
However, as of now I do not have a functioning board.
I am using the kernel build using the ELDK 3.1.1 tools and a file system
which was build using Montavista tools (DevRocket 1.1). Is that a problem???
The kernel is uncompressed on the board and loads, but the Login prompt
never comes up. Following are my boot up messages.
U-Boot 1.1.4 (Mar 21 2006 - 15:07:57)
CPU: MPC5200 v1.2 at 462 MHz
Bus 132 MHz, IPB 66 MHz, PCI 33 MHz
Board: Motorola MPC5200 (IceCube)
I2C: 85 kHz, ready
DRAM: 64 MB
FLASH: 8 MB
In: serial
Out: serial
Err: serial
Net: FEC ETHERNET
Type "run flash_nfs" to mount root filesystem over NFS
Hit any key to stop autoboot: 0
## Booting image at ff900000 ...
Image Name: Linux-2.4.25
Created: 2006-06-14 21:07:25 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 870906 Bytes = 850.5 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Memory BAT mapping: BAT2=64Mb, BAT3=0Mb, residual: 0Mb
Linux version 2.4.25 (root@localhost.localdomain) (gcc version 3.3.3 (DENX
ELDK
3.1.1 3.3.3-9)) #7 Wed Jun 14 16:02:04 CDT 2006
On node 0 totalpages: 16384
zone(0): 16384 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/mtdblock2 rw rootfstype=jffs2
ip=192.168.0.7:192.
168.0.2:192.168.0.2:255.255.255.0:cpua::off
Calibrating delay loop... 307.20 BogoMIPS
Memory: 62224k available (1492k kernel code, 460k data, 76k init, 0k
highmem)
Dentry cache hash table entries: 8192 (order: 4, 65536 bytes)
Inode cache hash table entries: 4096 (order: 3, 32768 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
POSIX conformance testing by UNIFIX
PCI: Probing PCI hardware
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
Journalled Block Device driver loaded
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc.
pty: 256 Unix98 ptys configured
devfs_register(ttyS): could not append to parent, err: -17
devfs_register(ttyS): could not append to parent, err: -17
devfs_register(cua): could not append to parent, err: -17
devfs_register(cua): could not append to parent, err: -17
ttyS0 on PSC1
ttyS1 on PSC2
ttyS2 on PSC3
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: loaded (max 8 devices)
SCSI subsystem driver Revision: 1.00
Icecube Bank 0: Found 1 x16 devices at 0x0 in 8-bit mode
Intel/Sharp Extended Query Table at 0x0031
cfi_cmdset_0001: Erase suspend on write enabled
Using buffer write method
Icecube flash bank 0: Using static image partition definition
Creating 3 MTD partitions on "Icecube Bank 0":
0x00000000-0x00100000 : "u-boot"
0x00100000-0x00200000 : "kernel"
0x00200000-0x00800000 : "jffs2"
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
host/usb-ohci.c: USB OHCI at membase 0xf0001000, IRQ 44
host/usb-ohci.c: usb-0, Built-In ohci
usb.c: new USB bus registered, assigned bus number 1
Product: USB OHCI Root Hub
SerialNumber: f0001000
hub.c: USB hub found
hub.c: 2 ports detected
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
eth0: Phy @ 0x0, type LXT971 (0x001378e2)
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
eth0: config: auto-negotiation off, 100FDX, 100HDX, 10FDX, 10HDX.
IP-Config: Complete:
device=eth0, addr=192.168.0.7, mask=255.255.255.0, gw=192.168.0.2,
host=cpua, domain=, nis-domain=(none),
bootserver=192.168.0.2, rootserver=192.168.0.2, rootpath=
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Empty flash at 0x0000fffc ends at 0x00010000
CLEANMARKER node found at 0x00010000, not first node in block (0x00000000)
Empty flash at 0x0002fffc ends at 0x00030000
CLEANMARKER node found at 0x00030000, not first node in block (0x00020000)
Empty flash at 0x0004fffc ends at 0x00050000
CLEANMARKER node found at 0x00050000, not first node in block (0x00040000)
Empty flash at 0x0006fffc ends at 0x00070000
CLEANMARKER node found at 0x00070000, not first node in block (0x00060000)
Empty flash at 0x0008fffc ends at 0x00090000
CLEANMARKER node found at 0x00090000, not first node in block (0x00080000)
Empty flash at 0x000afffc ends at 0x000b0000
CLEANMARKER node found at 0x000b0000, not first node in block (0x000a0000)
Empty flash at 0x000cfffc ends at 0x000d0000
CLEANMARKER node found at 0x000d0000, not first node in block (0x000c0000)
Empty flash at 0x000efffc ends at 0x000f0000
CLEANMARKER node found at 0x000f0000, not first node in block (0x000e0000)
Empty flash at 0x0010fffc ends at 0x00110000
CLEANMARKER node found at 0x00110000, not first node in block (0x00100000)
Empty flash at 0x0012fffc ends at 0x00130000
CLEANMARKER node found at 0x00130000, not first node in block (0x00120000)
CLEANMARKER node found at 0x00150000, not first node in block (0x00140000)
Empty flash at 0x0016fffc ends at 0x00170000
CLEANMARKER node found at 0x00170000, not first node in block (0x00160000)
Empty flash at 0x0018fffc ends at 0x00190000
CLEANMARKER node found at 0x00190000, not first node in block (0x00180000)
Empty flash at 0x001afffc ends at 0x001b0000
CLEANMARKER node found at 0x001b0000, not first node in block (0x001a0000)
Empty flash at 0x001cffe8 ends at 0x001d0000
CLEANMARKER node found at 0x001d0000, not first node in block (0x001c0000)
VFS: Mounted root (jffs2 filesystem).
Mounted devfs on /dev
Freeing unused kernel memory: 76k init
serial console detected. Disabling virtual terminals.
init started: BusyBox v0.60.3 (2004.01.09-22:53+0000) multi-call binary
System initialized
eth0: status: link up, 100 Mbps Full Duplex, auto-negotiation complete.
hub.c: Cannot enable port 2 of hub 1, disabling port.
hub.c: Maybe the USB cable is bad?
>> Is there another sequence of make commands that I need to follow to
>>create a
>> UBoot image?
>Not really.
>Note that above is for the old Lite5200 board. For the (newer)
>Lite5200B boards you must use latest version of U-Boot and Linux (top
>of tree from our git repositories), and "make lite5200b_config" to
>start.
The board we are using contains the Lite5200
The purpose for doing all this is to get the USB flash drive to work on the
board (read, write files to it)
Thanks again for all your help.
Orges
[-- Attachment #2: Type: text/html, Size: 37443 bytes --]
^ permalink raw reply
* Re: [OOPS] 2.6.17-rc3 on an mpc8241
From: Guennadi Liakhovetski @ 2006-06-14 21:01 UTC (permalink / raw)
To: Johannes Berg; +Cc: linuxppc-dev
In-Reply-To: <1150318658.13958.26.camel@johannes.berg>
On Wed, 14 Jun 2006, Johannes Berg wrote:
> On Wed, 2006-06-14 at 22:48 +0200, Guennadi Liakhovetski wrote:
> > Corrupted stack?...
>
> Looks weird.
> Enable slab debugging? :)
Compiling 2.6.17-rc5... And I don't know how easy it is to reproduce...
Once I have the kernel ready will try...
Thanks
Guennadi
---
Guennadi Liakhovetski
^ permalink raw reply
* Re: [OOPS] 2.6.17-rc3 on an mpc8241
From: Johannes Berg @ 2006-06-14 20:57 UTC (permalink / raw)
To: Guennadi Liakhovetski; +Cc: linuxppc-dev
In-Reply-To: <Pine.LNX.4.60.0606142245370.12545@poirot.grange>
[-- Attachment #1: Type: text/plain, Size: 143 bytes --]
On Wed, 2006-06-14 at 22:48 +0200, Guennadi Liakhovetski wrote:
> Corrupted stack?...
Looks weird.
Enable slab debugging? :)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]
^ permalink raw reply
* [OOPS] 2.6.17-rc3 on an mpc8241
From: Guennadi Liakhovetski @ 2006-06-14 20:48 UTC (permalink / raw)
To: linuxppc-dev
"dhclient eth1" (zd1211rw driver) caused the following:
Oops: kernel access of bad area, sig: 11 [#1]
NIP: C004151C LR: C0039850 CTR: 00000000
REGS: c6a15c70 TRAP: 0300 Not tainted (2.6.17-rc3-kuroboxHG)
MSR: 00009032 <EE,ME,IR,DR> CR: 44000488 XER: 00000000
DAR: 00000038, DSISR: 20000000
TASK = c7d4a850[2546] 'dhclient' THREAD: c6a14000
GPR00: 00030017 C6A15D20 C7D4A850 00000038 C03CBF00 00000000 00000038 C6A15D50
GPR08: 00000000 00000004 00000000 00000004 00000000 100383F4 C76557C8 00000001
GPR16: 00000000 C6A15D50 00000000 C6A15EA0 C6A15DF0 00000001 00000000 C75C7F00
GPR24: 30017000 00000000 00000000 C03CBF00 C7655868 30017000 C6A45E07 00000038
NIP [C004151C] put_page+0x0/0x40
LR [C0039850] do_generic_mapping_read+0x354/0x480
Call Trace:
[C6A15D20] [C0040EB0] page_cache_readahead+0xd0/0x224 (unreliable)
[C6A15D40] [C0039838] do_generic_mapping_read+0x33c/0x480
[C6A15DE0] [C003C004] __generic_file_aio_read+0x1b4/0x208
[C6A15E30] [C003C224] generic_file_aio_read+0x3c/0x5c
[C6A15E40] [C0059768] do_sync_read+0xc4/0x134
[C6A15EF0] [C0059874] vfs_read+0x9c/0x1a4
[C6A15F10] [C0059CA0] sys_read+0x4c/0x90
[C6A15F40] [C0004220] ret_from_syscall+0x0/0x38
Instruction dump:
912700e4 7d000124 4bffc4a9 80010014 38210010 7c0803a6 4e800020 812700e8
3929ffff 912700e8 7d000124 4bffffdc <80030000> 700a4000 40820034 80030004
Corrupted stack?...
Thanks
Guennadi
---
Guennadi Liakhovetski
^ permalink raw reply
* Re: USB flashdrive on Motorola MPC5200 (IceCube) board, linux ke rnel 2.4.20
From: Wolfgang Denk @ 2006-06-14 20:07 UTC (permalink / raw)
To: Furxhi, Orges; +Cc: linuxppc-embedded
In-Reply-To: <162B449665D6D643AD9E1D50FC6F4B1403F16D5F@mdcexc05.na.ops.local>
In message <162B449665D6D643AD9E1D50FC6F4B1403F16D5F@mdcexc05.na.ops.local> you wrote:
> I downloaded the kernel you recommended and now I am trying to build a UBoot
> image that I can load unto flash.
> I use the following commands:
> $ make mrproper
> $ make menuconfig
> (select arch/ppc/configs/icecube_5200_defconfig file, exit and save)
> $ make uImage
Try instead:
$ make mrproper
$ make icecube_5200_config
$ make oldconfig
$ make dep
$ make uImage
> Is there another sequence of make commands that I need to follow to create a
> UBoot image?
Not really.
Note that above is for the old Lite5200 board. For the (newer)
Lite5200B boards you must use latest version of U-Boot and Linux (top
of tree from our git repositories), and "make lite5200b_config" to
start.
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 greatest warriors are the ones who fight for peace."
- Holly Near
^ permalink raw reply
* Xilinx SystemACE driver for 2.6
From: G.Muruganandam @ 2006-06-14 18:35 UTC (permalink / raw)
To: linuxppc-embedded; +Cc: glikely
[-- Attachment #1: Type: text/plain, Size: 479 bytes --]
Hello g,
I am looking for the answer to your question regarding the System ACE
driver under 2.6
posted in the linuxppc-embedded@ozlabs.org.
Pl let me know whether it is ported to 2.6.
If yes, Would it be possible to share the source code?
Looking forward to hear from you.
Thanks
G.Muruganandam
Earlier post:
=========
Has anybody ported the SystemACE driver from 2.4 to 2.6 yet? If so,
where can I pull a patch from? Otherwise I'll start work on it.
Thanks,
g.
[-- Attachment #2: Type: text/html, Size: 599 bytes --]
^ permalink raw reply
* board initialization problem
From: Om Vadlapatla @ 2006-06-14 16:40 UTC (permalink / raw)
To: linuxppc-embedded@ozlabs.org, U-Boot-Users@lists.sourceforge.net
[-- Attachment #1: Type: text/plain, Size: 2344 bytes --]
K0: Original Montavista kernel
K1: Kernel without D-cache Adapted for 4x60(SDH 2/6
ch)
K2: Kernel with D-cache enabled for 4160 (SDH 6 ch)
Difference between K1 & K2:
1. D-cache (~/kernel2.4.17/arch/ppc/kernel/head.S)
here only one line difference.
2. Page table & cache buffer allocation
(~/kernel2.4.17/arch/ppc/8260_io/comproc.c)
I can send the difference only 4 lines only setting
the buffer arrays.
Target: 4160 (compat SDH unit)
Abatron: Jtag Debugger
fw4x60.cfg: old config file for Abatron
fw8270.cfg: new config file for Abatron
The tests tried using U-BOOT:
1. Loaded K1 onto target independent of Abatron
2. Loaded K2 onto target with Abatron fw8270.cfg
ran busy looptest for K1 & K2 result: K2 40 times
faster
3. Tried to load K2 to target without Abatron result:
Failed
Conclusions & comments:
There are significant differences between fw4x60.cfg &
fw8270.cfg.
These differences need to be incorporated in the new
Kernel (OR I am not sure about it but may be into the
Boot-loader).
Core Initialization file in kernel:
~/kernel2.4.17/arch/ppc/kernel/head.S
Speculated changes:
~/kernel2.4.17/arch/ppc/8260_io/comproc.c
It was speculated that the cached buffers triggered
the exception. And commproc.c was modified to make
those buffers uncacheable. But that made things worse:
invalidate_dcache_range() and flush_tlb_page() cause
another exception to occur (not identified).
U-boot initialization files:
~/u-boot/cpu/mpc8260
start.S, cpu_init.c
Both these files in u-boot are meant to initialize
the core & MMU.
If the config changes need to go into the kernel I am
not sure if it is the head.S file.
If the config changes need to go into the boot loader
I am not sure while the kernel opperates if there will
be any unpredictable behaviour.
Irrespective of where the changes go, the main task is
to analize each difference between fw4x60.cfg &
fw8270.cfg and develope the initialization code.
If any one has another plan of action please let me
know, I appreciate guidance.
Attached are the two config files.
Sincerely,
Om Vadlapatla
PS:- All I need is to load the new kernel with out a
glitch coz I can do it with the Abatron pluged in.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
[-- Attachment #2: 1384370366-fw4x60.cfg.txt --]
[-- Type: text/plain, Size: 5839 bytes --]
; -----------------------------------------------------------------------------
; Abatron bdiGDB configuration file for the FW4X60 platform
; single board computer running MontaVista Linux.
;
; The physical memory map is as follows:
; 0x00000000 - 0x0FFFFFFF 256MB 60x SDRAM on CS1 and CS2
; 0x30000000 - 0x33FFFFFF 64MB local SDRAM on CS5
; 0x40000000 - 0x41FFFFFF 32MB FPGA on CS6
; 0x50000000 - 0x50FFFFFF 16MB RTC on CS7
; 0x80000000 - 0x80007FFF 32KB IDE on CS9
; 0xF0000000 - 0xF001FFFF 128KB MPC8260 internal memory
; 0xFFE00000 - 0xFFFFFFFF 2MB Flash on CS0
; -----------------------------------------------------------------------------
;
[INIT]
WM32 0x000101A8 0xF0000000 ; IMMR (relocate internal memory)
WREG MSR 0x00000000 ; clear MSR
;WM32 0xF0010000 0x0A200000 ; SIUMCR
WM32 0xF0010004 0xFFFFFFC3 ; SYPCR (no watchdog)
WM32 0xF0010C80 0x00000001 ; SCCR
WM32 0xF0010024 0x80808000 ; BCR
WM8 0xF0010028 0x26 ; PPC_ACR:
WM32 0xF0010040 0x00004000 ; TESCR1:
WM32 0xF0010048 0x00004000 ; L_TESCR1:
;
;
; Memory controller
WM32 0xF0010104 0xFF000C54 ; OR0
WM32 0xF0010100 0xFF001001 ; BR0
;WM32 0xF0010100 0xFFE01001 ; BR0
;WM32 0xF0010104 0xFFE00844 ; OR0
WM32 0xF0010134 0xFE000008 ; OR6 FPGA
WM32 0xF0010130 0x40001001 ; BR6
WM32 0xF001013C 0xFF000C0C ; OR7 RTC
WM32 0xF0010138 0x50001001 ; BR7
WM32 0xF001014C 0xFFFF8008 ; OR9 IDE
WM32 0xF0010148 0x80001001 ; BR9
;
;
; Initialize the SDRAM on the 60x bus.
;
WM32 0xF001010C 0xF8002B00 ; OR1
WM32 0xF0010108 0x00000049 ; BR1
WM32 0xF0010114 0xF8002B00 ; OR2
WM32 0xF0010110 0x08000049 ; BR2
WM16 0xF0010184 0x4000 ; MPTPR
WM8 0xF001019C 0x7 ; PSRT
WM32 0xF0010190 0xAAAE245E ; PSDMR: Precharge all banks
WM8 0x00000000 0xFF ; Access SDRAM
WM32 0xF0010190 0x8AAE245E ; PSDMR: CBR Refresh
WM8 0x00000000 0xFF ; Access SDRAM
WM8 0x00000000 0xFF ; Access SDRAM
WM8 0x00000000 0xFF ; Access SDRAM
WM8 0x00000000 0xFF ; Access SDRAM
WM8 0x00000000 0xFF ; Access SDRAM
WM8 0x00000000 0xFF ; Access SDRAM
WM8 0x00000000 0xFF ; Access SDRAM
WM8 0x00000000 0xFF ; Access SDRAM
WM32 0xF0010190 0x9AAE245E ; PSDMR: Mode Register Write
WM8 0x00000000 0xFF ; Access SDRAM
WM32 0xF0010190 0xC2AE245E ; PSDMR: Normal operation and refresh enable
;
; Initialize the SDRAM on the local bus.
;
WM32 0xF001012C 0xFC002D00 ; OR5
WM32 0xF0010128 0x30001861 ; BR5
WM8 0xF00101A4 0x7 ; LSRT
WM32 0xF0010194 0xAA6A2556 ; LSDMR: Precharge all banks
WM8 0x30000000 0xFF ; Access SDRAM
WM32 0xF0010194 0x8A6A2556 ; LSDMR: CBR Refresh
WM8 0x30000000 0xFF ; Access SDRAM
WM8 0x30000000 0xFF ; Access SDRAM
WM8 0x30000000 0xFF ; Access SDRAM
WM8 0x30000000 0xFF ; Access SDRAM
WM8 0x30000000 0xFF ; Access SDRAM
WM8 0x30000000 0xFF ; Access SDRAM
WM8 0x30000000 0xFF ; Access SDRAM
WM8 0x30000000 0xFF ; Access SDRAM
WM32 0xF0010194 0x9A6A2556 ; LSDMR: Mode Register Write
WM8 0x30000000 0xFF ; Access SDRAM
WM32 0xF0010194 0xC26A2556 ; LSDMR: Normal operation and refresh enable
;
WM16 0x50800206 0x2000 ; Disable flash write protection
;
;
[TARGET]
CPUTYPE 8270 ; 603EV, 750, 8240, 8260, 750CX, or 7400
BDIMODE AGENT ; LOADONLY or AGENT
STARTUP RESET ; RESET, STOP, or RUN
JTAGCLOCK 3 ; 0=16.6MHz, 1=8.3MHz, 2=5.5MHz, 3=4.1MHz
BOOTADDR 0xFFF00100 ; 0xFFF00100 or 0x00000100
WORKSPACE 0x00000000 ; use SDRAM for 256 byte workspace
BREAKMODE HARD ; SOFT or HARD
VECTOR CATCH ; catch unhandled exceptions
DCACHE NOFLUSH ; FLUSH or NOFLUSH
POWERUP 3000
WAKEUP 3000
MMU XLAT 0xC0000000 ; kernel virtual base address
PTBASE 0x000000F0 ; address of page table pointer array
SIO 7 9600
;
;
;
[FLASH]
CHIPTYPE AM29BX16 ; AM29F, AM29BX8, AM29BX16, I28BX8, I28BX16,
; AT49, AT49X8, AT49X16, STRATAX8, STRATAX16
CHIPSIZE 0x200000 ; size of one flash chip in bytes
BUSWIDTH 16 ; flash bus width (8, 16, 32, or 64)
WORKSPACE 0xF0000000 ; use MPC8270 internal RAM for 2KB workspace
ERASE 0xFFE00000 CHIP ; erase entire Flash SIMM
;
;
;
[HOST]
IP 172.30.10.7 ; IP address of tftp server
FILE vmlinuz-est-sbc8260
FORMAT IMAGE 0x0 ; SREC, BIN, AOUT, ELF, IMAGE, or ROM
LOAD MANUAL ; MANUAL or AUTO
DEBUGPORT 2001 ; TCP port number for GDB
PROMPT FW4X60> ; Telnet prompt string
DUMP dump.bin ; default filename for DUMP command
;
;
;
[REGS]
DMM1 0xF0000000
FILE abatron/reg8260.def
[-- Attachment #3: 1432833698-FW8270.CFG --]
[-- Type: application/octet-stream, Size: 6635 bytes --]
; bdiGDB configuration file for MPC8270
; -----------------------------------------------
;
[INIT]
; init core register(MASTER)
WREG MSR 0x00000000 ;clear MSR
;WM32 0xF00101A8 0xF0000000 ;IMMR : internal space @ 0xF0000000
WM32 0xF0010004 0xFFFFFFC3 ;SYPCR: disable watchdog
WM32 0xF0010024 0x80800000 ;BCR:
WM8 0xF0010028 0x26 ;PPC_ACR:
WM32 0xF0010040 0x00004000 ;TESCR1:
WM32 0xF0010048 0x00004000 ;L_TESCR1:
;WM32 0xF0010C80 0x00000001 ;SCCR : normal operation
; init memory controller(master)
WM32 0xF0010104 0xFFE00C54 ;OR0: Flash 2MB, CS early negate, 5 w.s., Timing relax
WM32 0xF0010100 0xFFE01001 ;BR0: Flash @0xFF000000, 16bit, no parity
WM32 0xF001010C 0xF8002B00 ;OR1: 128MBYTE
WM32 0xF0010108 0x00000041 ;BR1: 60x-BUS
WM32 0xF0010114 0xF8002B00 ;OR2: 128MBYTE riki chg fc->f8
WM32 0xF0010110 0x08000041 ;BR2: 60x-BUS
;WM32 0xF001011C 0x00000000 ;OR3: 64MBYTE
;WM32 0xF0010118 0x00000000 ;BR3: 60x-BUS
WM32 0xF001012C 0xFC002F00 ;OR5: 64MBYTE
WM32 0xF0010128 0x30001861 ;BR5: LOCAL-BUS
WM32 0xF0010134 0xFC000008 ;OR6: MAINI-O
WM32 0xF0010130 0x40001001 ;BR6: 60x-BUS
WM32 0xF001013C 0xFF000C0C ;OR7: FPGA-IO
WM32 0xF0010138 0x50001001 ;BR7: 4MBYTE
;WM32 0xF0010144 0xFFFC0100 ;OR8: FUMEI-napa
;WM32 0xF0010140 0x58001081 ;BR8: FUMEI-napa
WM32 0xF001014C 0xFFFF0008 ;OR9: C-FLASH
WM32 0xF0010148 0x80001001 ;BR9: 60x-BUS
; init core register(SLAVE)
;WREG MSR 0x00000000 ;clear MSR
;WM32 0xFF0101A8 0xFF000000 ;IMMR : internal space @ 0xF0000000
WM32 0xFF010004 0xFFFFFFC3 ;SYPCR: disable watchdog
WM32 0xFF010024 0x80800000 ;BCR:
WM8 0xFF010028 0x27 ;PPC_ACR:
WM32 0xFF010040 0x00004000 ;TESCR1:
WM32 0xFF010048 0x00004000 ;L_TESCR1:
;WM32 0xFF010C80 0x00000001 ;SCCR : normal operation
; init SDRAM Init (PPC bus) for CS1&2
WM16 0xF0010184 0xF000 ;MPTPR
WM8 0xF001019C 0xF0 ;PSRT
WM32 0xF0010190 0xAB2DB4AE ;PSDMR: Precharge all banks
WM8 0x00000000 0xFF ;Access SDRAM
WM8 0x08000000 0xFF ;Access SDRAM
WM32 0xF0010190 0x8B2DB4AE ;PSDMR: CBR Refresh
WM8 0x00000000 0xFF ;Access SDRAM
WM8 0x00000000 0xFF ;Access SDRAM
WM8 0x00000000 0xFF ;Access SDRAM
WM8 0x00000000 0xFF ;Access SDRAM
WM8 0x00000000 0xFF ;Access SDRAM
WM8 0x00000000 0xFF ;Access SDRAM
WM8 0x00000000 0xFF ;Access SDRAM
WM8 0x00000000 0xFF ;Access SDRAM
WM8 0x08000000 0xFF ;Access SDRAM
WM8 0x08000000 0xFF ;Access SDRAM
WM8 0x08000000 0xFF ;Access SDRAM
WM8 0x08000000 0xFF ;Access SDRAM
WM8 0x08000000 0xFF ;Access SDRAM
WM8 0x08000000 0xFF ;Access SDRAM
WM8 0x08000000 0xFF ;Access SDRAM
WM8 0x08000000 0xFF ;Access SDRAM
WM32 0xF0010190 0x9B2DB4AE ;PSDMR: Mode Set
WM8 0x00088110 0xFF ;Access SDRAM
WM8 0x08088110 0xFF ;Access SDRAM
WM32 0xF0010190 0xc32DB4AE ;PSDMR: enable refresh, normal operation
WM16 0x50800206 0x2000 ;flash-protect-disable
; init SDRAM Init (LOCAL bus) for CS5
WM8 0xF00101A4 0xF0 ;LSRT
WM32 0xF0010194 0xAB41B4AE ;LSDMR: Precharge all banks
WM8 0x30000000 0xFF ;Access SDRAM
WM32 0xF0010194 0x8B41B4AE ;LSDMR: CBR Refresh
WM8 0x30000000 0xFF ;Access SDRAM
WM8 0x30000000 0xFF ;Access SDRAM
WM8 0x30000000 0xFF ;Access SDRAM
WM8 0x30000000 0xFF ;Access SDRAM
WM8 0x30000000 0xFF ;Access SDRAM
WM8 0x30000000 0xFF ;Access SDRAM
WM8 0x30000000 0xFF ;Access SDRAM
WM8 0x30000000 0xFF ;Access SDRAM
WM32 0xF0010194 0x9B41B4AE ;LSDMR: Mode Set
WM8 0x30044088 0xFF ;Access SDRAM
WM32 0xF0010194 0xC341B4AE ;LSDMR: enable refresh, normal operation
; init memory controller(slave)
;WM32 0xFF010104 0xFFE00C54 ;OR0: Flash 2MB, CS early negate, 5 w.s., Timing relax
WM32 0xFF010100 0x00000000 ;BR0: Flash @0xFF000000, 16bit, no parity
;WM32 0xFF01010C 0xF8002B00 ;OR1: 128MBYTE
;WM32 0xFF010108 0x00000041 ;BR1: 60x-BUS
;WM32 0xFF010114 0xF8002B00 ;OR2: 128MBYTE riki chg fc->f8
;WM32 0xFF010110 0x08000041 ;BR2: 60x-BUS
;WM32 0xFF01011C 0x00000000 ;OR3: 64MBYTE
;WM32 0xFF010118 0x00000000 ;BR3: 60x-BUS
;WM32 0xFF01012C 0xFC002F00 ;OR5: 64MBYTE
;WM32 0xFF010128 0x30001861 ;BR5: LOCAL-BUS
;WM32 0xFF010134 0xFC000008 ;OR6: MAINI-O
;WM32 0xFF010130 0x40001001 ;BR6: 60x-BUS
;WM32 0xFF01013C 0xFF000C0C ;OR7: FPGA-IO
;WM32 0xFF010138 0x50001001 ;BR7: 4MBYTE
;WM32 0xFF010144 0xFFFC0100 ;OR8: FUMEI-napa
;WM32 0xFF010140 0x58001081 ;BR8: FUMEI-napa
;WM32 0xFF01014C 0xFFFF0008 ;OR9: C-FLASH
;WM32 0xFF010148 0x80001001 ;BR9: 60x-BUS
[TARGET]
CPUTYPE 8270 ;the CPU type (603EV,750,8240,8260)
JTAGCLOCK 0 ;use 16 MHz JTAG clock
BOOTADDR 0xfff00100 ;boot address used for start-up break
WORKSPACE 0x0e000000 ;workspace in target RAM for fast download
BDIMODE AGENT ;the BDI working mode (LOADONLY | AGENT | GATEWAY)
BREAKMODE SOFT ;SOFT or HARD, HARD uses PPC hardware breakpoints
;STEPMODE HWBP ;TRACE or HWBP, HWPB uses a hardware breakpoint
VECTOR CATCH ;catch unhandled exceptions
DCACHE NOFLUSH ;data cache flushing (FLUSH | NOFLUSH)
;MMU XLAT ;translate effective to physical address
POWERUP 1000 ;start delay after power-up detected in ms
;REGLIST SPR ;select register to transfer to GDB
;REGLIST ALL ;select register to transfer to GDB
;VIO 7 9600 ;TCP port for virtual IO, BCSR1: enable RS232-1 !!!
;SIO 7 9600 ;TCP port for serial IO, check BCSR1: enable RS232-1 !!!
[HOST]
IP 192.168.0.3
FILE D:\cygwin\home\riki\ram-test-data\make_bin_inc_256M.bin
FORMAT BIN 0x00000000
LOAD MANUAL ;load code MANUAL or AUTO after reset
DEBUGPORT 2001
PROMPT MPC8270> ;new prompt for Telnet
DUMP D:\cygwin\home\riki\temp\dump.bin
[FLASH]
CHIPTYPE AM29BX16 ;Flash type (AM29F | AM29BX8 | AM29BX16 | I28BX8 | I28BX16)
;CHIPTYPE AM29BX8
CHIPSIZE 0x200000 ;The size of one flash chip in bytes (e.g. AM29F010 = 0x20000)
BUSWIDTH 16 ;The width of the flash memory bus in bits (8 | 16 | 32 | 64)
;WORKSPACE 0x04700000 ;workspace in dual port RAM
WORKSPACE 0x00000000 ;workspace in SDRAM
;FILE E:\tornado\target\config\ads8260\test.hex ;The file to program
FORMAT BIN
FILE D:\tftpboot\u-boot.bin
;
ERASE 0xFFE00000 CHIP ;ERASE WHOLE CHIP
[REGS]
DMM1 0xF0000000
FILE C:\BDI\CONFIG\reg8270.def
^ permalink raw reply
* RE: OpenFirmware framebuffer
From: Matt Sealey @ 2006-06-14 16:02 UTC (permalink / raw)
To: 'Benjamin Herrenschmidt'; +Cc: linuxppc-dev, 'Nathan Lynch'
In-Reply-To: <1150295351.5874.5.camel@localhost.localdomain>
Ben,
Please talk to Sven for a version, he is best to make sure you get something
that doesn't explode something you both know is important :)
--
Matt Sealey <matt@genesi-usa.com>
Manager, Genesi, Developer Relations
> -----Original Message-----
> From: Benjamin Herrenschmidt [mailto:benh@kernel.crashing.org]
>
> Better, send me a firmware image and I'll check what's up on
> my pegasos :)
^ permalink raw reply
* Re: [PATCH 5/10 v2] Add 8641 CPU and i8259 Setup
From: Jon Loeliger @ 2006-06-14 15:54 UTC (permalink / raw)
To: linuxppc-dev@ozlabs.org
In-Reply-To: <E1FojUI-0004N5-E7@jdl.com>
On Fri, 2006-06-09 at 11:05, Jon Loeliger wrote:
> > > + bl clear_bats
> > > bl load_up_mmu
> >
> > Why do you need to call clear_bats here ? load_up_mmu should load BATs.
> > If it doesn't handle the high BATs, then fix it :)
Ben,
This line item has finally come around on the guitar!
And I have a question for you...
How come this additional clear_bats call isn't seen
as a generic fix? It is possible that the bootloader
has left some crufty (high) BATs hanging around.
Or are you suggesting just adding something like:
li r10, 0
mtspr SPRN_DBATxU,r10
mtspr SPRN_DBATxL,r10
for x in (4 .. 7) to the tail end of load_up_mmu as
the general fix?
Thanks,
jdl
^ permalink raw reply
* [PATCH 0/3] powerpc: Instrument Hypervisor Calls: add sysfs files
From: Dave C Boutcher @ 2006-06-14 14:30 UTC (permalink / raw)
To: Mike Kravetz; +Cc: Bryan Rosenburg, linuxppc-dev, Christopher Yeoh
In-Reply-To: <20060614035420.GD6759@monkey.ibm.com>
On Tue, 13 Jun 2006 20:54:20 -0700, Mike Kravetz <kravetz@us.ibm.com> said:
>
> Make statistics available via files in sysfs.
> --
> Signed-off-by: Mike Kravetz <kravetz@us.ibm.com>
>
>
> diff -Naupr linux-2.6.17-rc6/arch/powerpc/kernel/sysfs.c linux-2.6.17-rc6.work/arch/powerpc/kernel/sysfs.c
> --- linux-2.6.17-rc6/arch/powerpc/kernel/sysfs.c 2006-06-06 00:57:02.000000000 +0000
> +++ linux-2.6.17-rc6.work/arch/powerpc/kernel/sysfs.c 2006-06-13 21:42:32.000000000 +0000
> @@ -356,6 +356,39 @@ static ssize_t show_physical_id(struct s
> }
> static SYSDEV_ATTR(physical_id, 0444, show_physical_id, NULL);
>
> +#ifdef CONFIG_HCALL_STATS
> +DECLARE_PER_CPU(struct hcall_stats[MAX_HCALL_OPCODES+1], hcall_stats);
> +
> +static ssize_t show_hcall_stats(struct sys_device *dev, char *buf)
> +{
> + struct cpu *cpu = container_of(dev, struct cpu, sysdev);
> + struct hcall_stats *hs = per_cpu(hcall_stats, cpu->sysdev.id);
> + size_t rc = 0;
> + size_t b_written = 0;
> + size_t b_remain = PAGE_SIZE;
> + unsigned long i;
> +
> + for (i=0; i<MAX_HCALL_OPCODES+1; i++){
> + if (!hs[i].num_calls)
> + continue;
> +
> + b_written = snprintf(buf+rc, b_remain,
> + "%lu %lu %lu\n",
> + i<<2, hs[i].num_calls, hs[i].total_time);
> +
> + if (b_written >= b_remain)
> + break; /* end of buffer */
> +
> + rc += b_written;
> + b_remain -= b_written;
> + }
> +
> + return rc;
> +}
> +
You're violating the "one value per file" rule for sysfs. Ware the
wrath of Greg KH.
Dave B
^ permalink raw reply
* RE: [PATCH/2.6.17-rc4 8/10] Add tsi108 8250 serial support
From: Adrian Cox @ 2006-06-14 14:25 UTC (permalink / raw)
To: Zang Roy-r61911
Cc: Alexandre.Bounine, Russell King, linux-kernel, linuxppc-dev list,
Paul Mackerras, linux-serial, Yang Xin-Xin-r48390
In-Reply-To: <9FCDBA58F226D911B202000BDBAD4673069C3C3D@zch01exm40.ap.freescale.net>
On Tue, 2006-06-13 at 13:39 +0800, Zang Roy-r61911 wrote:
> The reason is that the serial port on tsi108/9 is a bit difference with the
> standard 8250 serial port. the patch deal with the difference.
> The prefixed ">" is caused by "Fw" the email. Sorry for that. The following
> is the original patch.
The problem I see is that the code uses a CONFIG option, to change the
behaviour of the generic 8250 driver. What happens if somebody adds a
PCI serial card to a tsi108 based machine?
Perhaps you should define a new value for uart_8250_port.port.iotype,
and add code to serial_in and serial_out to handle the IIR register.
--
Adrian Cox <adrian@humboldt.co.uk>
^ permalink raw reply
* Re: USB flashdrive on Motorola MPC5200 (IceCube) board, linux kernel 2.4.20
From: Igor Luri @ 2006-06-14 15:49 UTC (permalink / raw)
To: Furxhi, Orges; +Cc: linuxppc-embedded
In-Reply-To: <162B449665D6D643AD9E1D50FC6F4B1403F16D5F@mdcexc05.na.ops.local>
We use the following secuence, after linux kernel is configured:
make clean
make dep
make uImage
Furxhi, Orges wrote:
>I downloaded the kernel you recommended and now I am trying to build a UBoot
>image that I can load unto flash.
>I use the following commands:
>$ make mrproper
>$ make menuconfig
> (select arch/ppc/configs/icecube_5200_defconfig file, exit and save)
>$ make uImage
>
>I can not find the UBoot image (/arch/ppc/boot/images/)
>I get the following error message after I execute $ make uImage:
>...
>/bin/sh: line 1: scripts/mkdep: Invalid argument
>make: *** [dep-files] Error 126
>
>Is there another sequence of make commands that I need to follow to create a
>UBoot image?
>
>
>Thanks,
>
>Orges
>
>-----Original Message-----
>From: Igor Luri [mailto:iluri@fagorautomation.es]
>Sent: Wednesday, June 14, 2006 8:57 AM
>To: Furxhi, Orges
>Cc: linuxppc-embedded@ozlabs.org
>Subject: Re: USB flashdrive on Motorola MPC5200 (IceCube) board, linux
>kernel 2.4.20
>
>It is posible that your kernel uses old USB code. We also have an
>Icecube board, the same board a yours, with linux 2.4.25 version from
>DENX and USB works well.
>
>You can try with this kernel:
>
>ftp://ftp.denx.de/pub/linux/linuxppc_2_4_devel-2006-04-06-1735.tar.bz2
>
>
>Hope this helps.
>
>
>Furxhi, Orges wrote:
>
>
>
>>Thank you for your help.
>>
>>I am using a Memorex travel drive 2.0 (512 MB), and I also have a
>>Intelligent Stick 2.0 from GE.
>>When I plug in the Memorex stick the following appears on the terminal :
>> # hub.c: new USB device builtin-1, assigned address 2
>> usb.c: USB device not accepting new address=2 (error=-110)
>> hub.c: new USB device builtin-1, assigned address 3
>> usb.c: USB device not accepting new address=3 (error=-110)
>>
>>When I plug in the GE stick nothing shows on the terminal, but when I
>>
>>
>remove
>
>
>>it the following message comes up:
>> # hub.c: connect-debounce failed, port 1 disabled
>>
>>Both the USB flash drives work on my Dell PC with RedHat 9.0 (2.4.20
>>kernel).
>>
>>Orges
>>
>>
>>
>>-----Original Message-----
>>From: Igor Luri [mailto:iluri@fagorautomation.es]
>>Sent: Wednesday, June 14, 2006 3:07 AM
>>To: Furxhi, Orges
>>Cc: linuxppc-embedded@ozlabs.org
>>Subject: Re: USB flashdrive on Motorola MPC5200 (IceCube) board, linux
>>kernel 2.4.20
>>
>>What kind of USB flash drive are you using? Linux doesn't detect your
>>device.
>>
>>When you plug/unplug a USB device you have to get something like this:
>>
>> hub.c: new USB device 0-1, assigned address 2
>> scsi0 : SCSI emulation for USB Mass Storage devices
>> Vendor: Model: USB DISK Pro Rev: 1.00
>> Type: Direct-Access ANSI SCSI revision: 02
>> Attached scsi removable disk sda at scsi0, channel 0, id 0,
>> lun 0
>> SCSI device sda: 240640 512-byte hdwr sectors (123 MB)
>> sda: Write Protect is off
>> sda: sda1
>>
>> usb.c: USB disconnect on device 0-1 address 2
>>
>>
>>Are you sure that this device is supported in your Linux configuration?
>>
>>
>>
>>Furxhi, Orges wrote:
>>
>>
>>
>>
>>
>>>Hi all,
>>>
>>>I have been trying for days now to get my usb flashdrive to work on my
>>>Motorola MPC5200 (IceCube) board running on the 2.4.20 linux kernel. I
>>>have followed the instruction in this Flash Memory HOWTO article
>>>(http://www.tldp.org/HOWTO/Flash-Memory-HOWTO/index.html), but I have
>>>had no success.
>>>
>>>When I mount the usbfs filesystem (mount -t usbfs none /proc/bus/usb/)
>>>the following 3 items are created in the /proc/bus/usb/ directory:
>>>
>>>dr-xr-xr-x 1 root root 0 Jan 1 00:12 001
>>>
>>>-r--r--r-- 1 root root 0 Jan 1 00:12 devices
>>>
>>>-r--r--r-- 1 root root 0 Jan 1 00:12 drivers
>>>
>>># cat devices shows:
>>>
>>>T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
>>>
>>>B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
>>>
>>>D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
>>>
>>>P: Vendor=0000 ProdID=0000 Rev= 0.00
>>>
>>>S: Product=USB OHCI Root Hub
>>>
>>>S: SerialNumber=f0001000
>>>
>>>C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
>>>
>>>I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
>>>
>>>E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
>>>
>>># cat drivers shows
>>>
>>>usbdevfs
>>>
>>>hub
>>>
>>>usb-storage
>>>
>>>In the this Flash Memory-HOWTO it is mentioned that the usb-storage-x
>>>directory will be created in the /proc/scsi/ directory, but I do not
>>>see it on my system. Also the contents of /proc/scsi/scsi are
>>>"Attached devices: none".
>>>
>>>Following are my boot up messages:
>>>
>>>U-Boot 1.1.4 (Mar 21 2006 - 15:07:57)
>>>
>>>CPU: MPC5200 v1.2 at 462 MHz
>>>
>>>Bus 132 MHz, IPB 66 MHz, PCI 33 MHz
>>>
>>>Board: Motorola MPC5200 (IceCube)
>>>
>>>I2C: 85 kHz, ready
>>>
>>>DRAM: 64 MB
>>>
>>>FLASH: 8 MB
>>>
>>>In: serial
>>>
>>>Out: serial
>>>
>>>Err: serial
>>>
>>>Net: FEC ETHERNET
>>>
>>>Type "run flash_nfs" to mount root filesystem over NFS
>>>
>>>Hit any key to stop autoboot: 0
>>>
>>>## Booting image at ff900000 ...
>>>
>>>Image Name: Linux-2.4.20_mvl31-lite5200
>>>
>>>Created: 2006-06-13 21:40:05 UTC
>>>
>>>Image Type: PowerPC Linux Kernel Image (gzip compressed)
>>>
>>>Data Size: 989480 Bytes = 966.3 kB
>>>
>>>Load Address: 00000000
>>>
>>>Entry Point: 00000000
>>>
>>>Verifying Checksum ... OK
>>>
>>>Uncompressing Kernel Image ... OK
>>>
>>>Memory BAT mapping: BAT2=64Mb, BAT3=0Mb, residual: 0Mb
>>>
>>>Linux version 2.4.20_mvl31-lite5200 (ofurxhi@mdc58503) (gcc version
>>>3.3.1 (Monta
>>>
>>>Vista 3.3.1-7.0.13.0500039 2005-01-12)) #11 Tue Jun 13 16:32:09 CDT 2006
>>>
>>>On node 0 totalpages: 16384
>>>
>>>zone(0): 16384 pages.
>>>
>>>zone(1): 0 pages.
>>>
>>>zone(2): 0 pages.
>>>
>>>Kernel command line: root=/dev/mtdblock2 rw rootfstype=jffs2
>>>ip=192.168.0.7:192.
>>>
>>>168.0.2:192.168.0.2:255.255.255.0:cpua::off
>>>
>>>frequencies: cpu=461995100, bus=131998608, ipb=65999304, pci=32999652
>>>
>>>Calibrating delay loop... 307.20 BogoMIPS
>>>
>>>Memory: 62460k available (1540k kernel code, 524k data, 240k init, 0k
>>>highmem)
>>>
>>>Dentry cache hash table entries: 8192 (order: 4, 65536 bytes)
>>>
>>>Inode cache hash table entries: 4096 (order: 3, 32768 bytes)
>>>
>>>Mount-cache hash table entries: 1024 (order: 1, 8192 bytes)
>>>
>>>Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)
>>>
>>>Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
>>>
>>>POSIX conformance testing by UNIFIX
>>>
>>>PCI: Probing PCI hardware
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:00.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:01.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:02.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:03.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:04.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:05.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:06.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:07.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:08.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:09.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:0a.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:0b.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:0c.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:0d.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:0e.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:0f.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:10.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:11.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:12.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:13.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:14.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:15.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:16.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:17.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:18.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:19.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:1a.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:1b.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:1c.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:1d.0
>>>
>>>PCI: Cannot allocate resource region 1 of device 00:1e.0
>>>
>>>Linux NET4.0 for Linux 2.4
>>>
>>>Based upon Swansea University Computer Society NET3.039
>>>
>>>Initializing RT netlink socket
>>>
>>>LSP Revision 52
>>>
>>>ikconfig 0.5 with /proc/ikconfig
>>>
>>>Starting kswapd
>>>
>>>Disabling the Out Of Memory Killer
>>>
>>>Journalled Block Device driver loaded
>>>
>>>devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
>>>
>>>devfs: boot_options: 0x1
>>>
>>>JFFS version 1.0, (C) 1999, 2000 Axis Communications AB
>>>
>>>JFFS2 version 2.1. (C) 2001, 2002 Red Hat, Inc., designed by Axis
>>>Communications
>>>
>>>AB.
>>>
>>>pty: 256 Unix98 ptys configured
>>>
>>>RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
>>>
>>>loop: loaded (max 8 devices)
>>>
>>>Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky
>>>
>>>SCSI subsystem driver Revision: 1.00
>>>
>>>kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
>>>
>>>kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
>>>
>>>NO QRY response
>>>
>>>cfi_cmdset_0001: Erase suspend on write enabled
>>>
>>>Using buffer write method
>>>
>>>Icecube flash bank 0: Using static image partition definition
>>>
>>>Creating 3 MTD partitions on "Icecube Bank 0":
>>>
>>>0x00000000-0x00100000 : "u-boot"
>>>
>>>0x00100000-0x00200000 : "kernel"
>>>
>>>0x00200000-0x00800000 : "jffs2"
>>>
>>>usb.c: registered new driver usbdevfs
>>>
>>>usb.c: registered new driver hub
>>>
>>>usb-ohci.c: USB OHCI at membase 0xf0001000, IRQ 44
>>>
>>>usb.c: new USB bus registered, assigned bus number 1
>>>
>>>Product: USB OHCI Root Hub
>>>
>>>SerialNumber: f0001000
>>>
>>>hub.c: USB hub found
>>>
>>>hub.c: 2 ports detected
>>>
>>>Initializing USB Mass Storage driver...
>>>
>>>usb.c: registered new driver usb-storage
>>>
>>>USB Mass Storage support registered.
>>>
>>>eth0: Phy @ 0x0, type LXT971 (0x001378e2)
>>>
>>>NET4: Linux TCP/IP 1.0 for NET4.0
>>>
>>>IP Protocols: ICMP, UDP, TCP, IGMP
>>>
>>>IP: routing cache hash table of 512 buckets, 4Kbytes
>>>
>>>TCP: Hash tables configured (established 4096 bind 8192)
>>>
>>>eth0: config: auto-negotiation off, 100HDX, 10HDX.
>>>
>>>IP-Config: Complete:
>>>
>>>device=eth0, addr=192.168.0.7, mask=255.255.255.0, gw=192.168.0.2,
>>>
>>>host=cpua, domain=, nis-domain=(none),
>>>
>>>bootserver=192.168.0.2, rootserver=192.168.0.2, rootpath=
>>>
>>>NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
>>>
>>>Empty flash at 0x0000fffc ends at 0x00010000
>>>
>>>CLEANMARKER node found at 0x00010000, not first node in block (0x00000000)
>>>
>>>Empty flash at 0x0002fffc ends at 0x00030000
>>>
>>>CLEANMARKER node found at 0x00030000, not first node in block (0x00020000)
>>>
>>>Empty flash at 0x0004fffc ends at 0x00050000
>>>
>>>CLEANMARKER node found at 0x00050000, not first node in block (0x00040000)
>>>
>>>Empty flash at 0x0006fffc ends at 0x00070000
>>>
>>>CLEANMARKER node found at 0x00070000, not first node in block (0x00060000)
>>>
>>>Empty flash at 0x0008fffc ends at 0x00090000
>>>
>>>CLEANMARKER node found at 0x00090000, not first node in block (0x00080000)
>>>
>>>Empty flash at 0x000afffc ends at 0x000b0000
>>>
>>>CLEANMARKER node found at 0x000b0000, not first node in block (0x000a0000)
>>>
>>>Empty flash at 0x000cfffc ends at 0x000d0000
>>>
>>>CLEANMARKER node found at 0x000d0000, not first node in block (0x000c0000)
>>>
>>>Empty flash at 0x000efffc ends at 0x000f0000
>>>
>>>CLEANMARKER node found at 0x000f0000, not first node in block (0x000e0000)
>>>
>>>Empty flash at 0x0010fffc ends at 0x00110000
>>>
>>>CLEANMARKER node found at 0x00110000, not first node in block (0x00100000)
>>>
>>>Empty flash at 0x0012fffc ends at 0x00130000
>>>
>>>CLEANMARKER node found at 0x00130000, not first node in block (0x00120000)
>>>
>>>Empty flash at 0x0014fffc ends at 0x00150000
>>>
>>>CLEANMARKER node found at 0x00150000, not first node in block (0x00140000)
>>>
>>>Empty flash at 0x0016fffc ends at 0x00170000
>>>
>>>CLEANMARKER node found at 0x00170000, not first node in block (0x00160000)
>>>
>>>Empty flash at 0x0018fffc ends at 0x00190000
>>>
>>>CLEANMARKER node found at 0x00190000, not first node in block (0x00180000)
>>>
>>>Empty flash at 0x001afffc ends at 0x001b0000
>>>
>>>CLEANMARKER node found at 0x001b0000, not first node in block (0x001a0000)
>>>
>>>Empty flash at 0x001cfffc ends at 0x001d0000
>>>
>>>CLEANMARKER node found at 0x001d0000, not first node in block (0x001c0000)
>>>
>>>Empty flash at 0x001efffc ends at 0x001f0000
>>>
>>>CLEANMARKER node found at 0x001f0000, not first node in block (0x001e0000)
>>>
>>>Empty flash at 0x0020fffc ends at 0x00210000
>>>
>>>CLEANMARKER node found at 0x00210000, not first node in block (0x00200000)
>>>
>>>Empty flash at 0x0022fffc ends at 0x00230000
>>>
>>>CLEANMARKER node found at 0x00230000, not first node in block (0x00220000)
>>>
>>>Empty flash at 0x0024fffc ends at 0x00250000
>>>
>>>CLEANMARKER node found at 0x00250000, not first node in block (0x00240000)
>>>
>>>Empty flash at 0x0026fffc ends at 0x00270000
>>>
>>>CLEANMARKER node found at 0x00270000, not first node in block (0x00260000)
>>>
>>>VFS: Mounted root (jffs2 filesystem).
>>>
>>>Mounted devfs on /dev
>>>
>>>Freeing unused kernel memory: 240k init
>>>
>>>serial console detected. Disabling virtual terminals.
>>>
>>>init started: BusyBox v0.60.3 (2004.01.09-22:53+0000) multi-call binary
>>>
>>>Initializing iocspi
>>>
>>>Warning: loading /lib/modules/iocspim.o will taint the kernel: no license
>>>
>>>See http://www.tux.org/lkml/#export-tainted for information about
>>>tainted modu
>>>
>>>les
>>>
>>>iocspi: release_20060418
>>>
>>>iocspi: major 254.
>>>
>>>Module iocspim loaded, with warnings
>>>
>>>Initializing canspi
>>>
>>>Warning: loading /lib/modules/canspim.o will taint the kernel: no license
>>>
>>>See http://www.tux.org/lkml/#export-tainted for information about
>>>tainted modu
>>>
>>>les
>>>
>>>canspi: init_module()
>>>
>>>canspi: init_module(): sema_init
>>>
>>>canspi: init_module(): register_chrdev
>>>
>>>canspi: major 253.
>>>
>>>canspi: micro_config()
>>>
>>>canspi: micro_config: PSC request_irq failed (0)
>>>
>>>canspi: micro_config psc=f0002400 cdm=f0000200 gpio=f0000b00
>>>portcfg=10051004
>>>
>>>Module canspim loaded, with warnings
>>>
>>>Initializing iocdrv
>>>
>>>Warning: loading /lib/modules/iocdrvm.o will taint the kernel: no license
>>>
>>>See http://www.tux.org/lkml/#export-tainted for information about
>>>tainted modu
>>>
>>>les
>>>
>>>iocdrv: release_20060502
>>>
>>>iocdrv: major 252.
>>>
>>>Module iocdrvm loaded, with warnings
>>>
>>>System initialized
>>>
>>>MontaVista(R) Linux(R) Professional Edition 3.1
>>>
>>>cpua login:
>>>
>>>Any help would be highly appreciated.
>>>
>>>Thank you,
>>>
>>>Orges Furxhi
>>>
>>>------------------------------------------------------------------------
>>>
>>>_______________________________________________
>>>Linuxppc-embedded mailing list
>>>Linuxppc-embedded@ozlabs.org
>>>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>>
>>>
>>>
>>>
>>>
^ permalink raw reply
* RE: USB flashdrive on Motorola MPC5200 (IceCube) board, linux ke rnel 2.4.20
From: Furxhi, Orges @ 2006-06-14 15:36 UTC (permalink / raw)
To: Igor Luri, Furxhi, Orges; +Cc: linuxppc-embedded
I downloaded the kernel you recommended and now I am trying to build a UBoot
image that I can load unto flash.
I use the following commands:
$ make mrproper
$ make menuconfig
(select arch/ppc/configs/icecube_5200_defconfig file, exit and save)
$ make uImage
I can not find the UBoot image (/arch/ppc/boot/images/)
I get the following error message after I execute $ make uImage:
...
/bin/sh: line 1: scripts/mkdep: Invalid argument
make: *** [dep-files] Error 126
Is there another sequence of make commands that I need to follow to create a
UBoot image?
Thanks,
Orges
-----Original Message-----
From: Igor Luri [mailto:iluri@fagorautomation.es]
Sent: Wednesday, June 14, 2006 8:57 AM
To: Furxhi, Orges
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: USB flashdrive on Motorola MPC5200 (IceCube) board, linux
kernel 2.4.20
It is posible that your kernel uses old USB code. We also have an
Icecube board, the same board a yours, with linux 2.4.25 version from
DENX and USB works well.
You can try with this kernel:
ftp://ftp.denx.de/pub/linux/linuxppc_2_4_devel-2006-04-06-1735.tar.bz2
Hope this helps.
Furxhi, Orges wrote:
>Thank you for your help.
>
>I am using a Memorex travel drive 2.0 (512 MB), and I also have a
>Intelligent Stick 2.0 from GE.
>When I plug in the Memorex stick the following appears on the terminal :
> # hub.c: new USB device builtin-1, assigned address 2
> usb.c: USB device not accepting new address=2 (error=-110)
> hub.c: new USB device builtin-1, assigned address 3
> usb.c: USB device not accepting new address=3 (error=-110)
>
>When I plug in the GE stick nothing shows on the terminal, but when I
remove
>it the following message comes up:
> # hub.c: connect-debounce failed, port 1 disabled
>
>Both the USB flash drives work on my Dell PC with RedHat 9.0 (2.4.20
>kernel).
>
>Orges
>
>
>
>-----Original Message-----
>From: Igor Luri [mailto:iluri@fagorautomation.es]
>Sent: Wednesday, June 14, 2006 3:07 AM
>To: Furxhi, Orges
>Cc: linuxppc-embedded@ozlabs.org
>Subject: Re: USB flashdrive on Motorola MPC5200 (IceCube) board, linux
>kernel 2.4.20
>
>What kind of USB flash drive are you using? Linux doesn't detect your
>device.
>
>When you plug/unplug a USB device you have to get something like this:
>
> hub.c: new USB device 0-1, assigned address 2
> scsi0 : SCSI emulation for USB Mass Storage devices
> Vendor: Model: USB DISK Pro Rev: 1.00
> Type: Direct-Access ANSI SCSI revision: 02
> Attached scsi removable disk sda at scsi0, channel 0, id 0,
> lun 0
> SCSI device sda: 240640 512-byte hdwr sectors (123 MB)
> sda: Write Protect is off
> sda: sda1
>
> usb.c: USB disconnect on device 0-1 address 2
>
>
>Are you sure that this device is supported in your Linux configuration?
>
>
>
>Furxhi, Orges wrote:
>
>
>
>>Hi all,
>>
>>I have been trying for days now to get my usb flashdrive to work on my
>>Motorola MPC5200 (IceCube) board running on the 2.4.20 linux kernel. I
>>have followed the instruction in this Flash Memory HOWTO article
>>(http://www.tldp.org/HOWTO/Flash-Memory-HOWTO/index.html), but I have
>>had no success.
>>
>>When I mount the usbfs filesystem (mount -t usbfs none /proc/bus/usb/)
>>the following 3 items are created in the /proc/bus/usb/ directory:
>>
>>dr-xr-xr-x 1 root root 0 Jan 1 00:12 001
>>
>>-r--r--r-- 1 root root 0 Jan 1 00:12 devices
>>
>>-r--r--r-- 1 root root 0 Jan 1 00:12 drivers
>>
>># cat devices shows:
>>
>>T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
>>
>>B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
>>
>>D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
>>
>>P: Vendor=0000 ProdID=0000 Rev= 0.00
>>
>>S: Product=USB OHCI Root Hub
>>
>>S: SerialNumber=f0001000
>>
>>C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
>>
>>I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
>>
>>E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
>>
>># cat drivers shows
>>
>>usbdevfs
>>
>>hub
>>
>>usb-storage
>>
>>In the this Flash Memory-HOWTO it is mentioned that the usb-storage-x
>>directory will be created in the /proc/scsi/ directory, but I do not
>>see it on my system. Also the contents of /proc/scsi/scsi are
>>"Attached devices: none".
>>
>>Following are my boot up messages:
>>
>>U-Boot 1.1.4 (Mar 21 2006 - 15:07:57)
>>
>>CPU: MPC5200 v1.2 at 462 MHz
>>
>>Bus 132 MHz, IPB 66 MHz, PCI 33 MHz
>>
>>Board: Motorola MPC5200 (IceCube)
>>
>>I2C: 85 kHz, ready
>>
>>DRAM: 64 MB
>>
>>FLASH: 8 MB
>>
>>In: serial
>>
>>Out: serial
>>
>>Err: serial
>>
>>Net: FEC ETHERNET
>>
>>Type "run flash_nfs" to mount root filesystem over NFS
>>
>>Hit any key to stop autoboot: 0
>>
>>## Booting image at ff900000 ...
>>
>>Image Name: Linux-2.4.20_mvl31-lite5200
>>
>>Created: 2006-06-13 21:40:05 UTC
>>
>>Image Type: PowerPC Linux Kernel Image (gzip compressed)
>>
>>Data Size: 989480 Bytes = 966.3 kB
>>
>>Load Address: 00000000
>>
>>Entry Point: 00000000
>>
>>Verifying Checksum ... OK
>>
>>Uncompressing Kernel Image ... OK
>>
>>Memory BAT mapping: BAT2=64Mb, BAT3=0Mb, residual: 0Mb
>>
>>Linux version 2.4.20_mvl31-lite5200 (ofurxhi@mdc58503) (gcc version
>>3.3.1 (Monta
>>
>>Vista 3.3.1-7.0.13.0500039 2005-01-12)) #11 Tue Jun 13 16:32:09 CDT 2006
>>
>>On node 0 totalpages: 16384
>>
>>zone(0): 16384 pages.
>>
>>zone(1): 0 pages.
>>
>>zone(2): 0 pages.
>>
>>Kernel command line: root=/dev/mtdblock2 rw rootfstype=jffs2
>>ip=192.168.0.7:192.
>>
>>168.0.2:192.168.0.2:255.255.255.0:cpua::off
>>
>>frequencies: cpu=461995100, bus=131998608, ipb=65999304, pci=32999652
>>
>>Calibrating delay loop... 307.20 BogoMIPS
>>
>>Memory: 62460k available (1540k kernel code, 524k data, 240k init, 0k
>>highmem)
>>
>>Dentry cache hash table entries: 8192 (order: 4, 65536 bytes)
>>
>>Inode cache hash table entries: 4096 (order: 3, 32768 bytes)
>>
>>Mount-cache hash table entries: 1024 (order: 1, 8192 bytes)
>>
>>Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)
>>
>>Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
>>
>>POSIX conformance testing by UNIFIX
>>
>>PCI: Probing PCI hardware
>>
>>PCI: Cannot allocate resource region 1 of device 00:00.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:01.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:02.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:03.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:04.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:05.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:06.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:07.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:08.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:09.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:0a.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:0b.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:0c.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:0d.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:0e.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:0f.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:10.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:11.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:12.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:13.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:14.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:15.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:16.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:17.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:18.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:19.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:1a.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:1b.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:1c.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:1d.0
>>
>>PCI: Cannot allocate resource region 1 of device 00:1e.0
>>
>>Linux NET4.0 for Linux 2.4
>>
>>Based upon Swansea University Computer Society NET3.039
>>
>>Initializing RT netlink socket
>>
>>LSP Revision 52
>>
>>ikconfig 0.5 with /proc/ikconfig
>>
>>Starting kswapd
>>
>>Disabling the Out Of Memory Killer
>>
>>Journalled Block Device driver loaded
>>
>>devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
>>
>>devfs: boot_options: 0x1
>>
>>JFFS version 1.0, (C) 1999, 2000 Axis Communications AB
>>
>>JFFS2 version 2.1. (C) 2001, 2002 Red Hat, Inc., designed by Axis
>>Communications
>>
>>AB.
>>
>>pty: 256 Unix98 ptys configured
>>
>>RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
>>
>>loop: loaded (max 8 devices)
>>
>>Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky
>>
>>SCSI subsystem driver Revision: 1.00
>>
>>kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
>>
>>kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
>>
>>NO QRY response
>>
>>cfi_cmdset_0001: Erase suspend on write enabled
>>
>>Using buffer write method
>>
>>Icecube flash bank 0: Using static image partition definition
>>
>>Creating 3 MTD partitions on "Icecube Bank 0":
>>
>>0x00000000-0x00100000 : "u-boot"
>>
>>0x00100000-0x00200000 : "kernel"
>>
>>0x00200000-0x00800000 : "jffs2"
>>
>>usb.c: registered new driver usbdevfs
>>
>>usb.c: registered new driver hub
>>
>>usb-ohci.c: USB OHCI at membase 0xf0001000, IRQ 44
>>
>>usb.c: new USB bus registered, assigned bus number 1
>>
>>Product: USB OHCI Root Hub
>>
>>SerialNumber: f0001000
>>
>>hub.c: USB hub found
>>
>>hub.c: 2 ports detected
>>
>>Initializing USB Mass Storage driver...
>>
>>usb.c: registered new driver usb-storage
>>
>>USB Mass Storage support registered.
>>
>>eth0: Phy @ 0x0, type LXT971 (0x001378e2)
>>
>>NET4: Linux TCP/IP 1.0 for NET4.0
>>
>>IP Protocols: ICMP, UDP, TCP, IGMP
>>
>>IP: routing cache hash table of 512 buckets, 4Kbytes
>>
>>TCP: Hash tables configured (established 4096 bind 8192)
>>
>>eth0: config: auto-negotiation off, 100HDX, 10HDX.
>>
>>IP-Config: Complete:
>>
>>device=eth0, addr=192.168.0.7, mask=255.255.255.0, gw=192.168.0.2,
>>
>>host=cpua, domain=, nis-domain=(none),
>>
>>bootserver=192.168.0.2, rootserver=192.168.0.2, rootpath=
>>
>>NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
>>
>>Empty flash at 0x0000fffc ends at 0x00010000
>>
>>CLEANMARKER node found at 0x00010000, not first node in block (0x00000000)
>>
>>Empty flash at 0x0002fffc ends at 0x00030000
>>
>>CLEANMARKER node found at 0x00030000, not first node in block (0x00020000)
>>
>>Empty flash at 0x0004fffc ends at 0x00050000
>>
>>CLEANMARKER node found at 0x00050000, not first node in block (0x00040000)
>>
>>Empty flash at 0x0006fffc ends at 0x00070000
>>
>>CLEANMARKER node found at 0x00070000, not first node in block (0x00060000)
>>
>>Empty flash at 0x0008fffc ends at 0x00090000
>>
>>CLEANMARKER node found at 0x00090000, not first node in block (0x00080000)
>>
>>Empty flash at 0x000afffc ends at 0x000b0000
>>
>>CLEANMARKER node found at 0x000b0000, not first node in block (0x000a0000)
>>
>>Empty flash at 0x000cfffc ends at 0x000d0000
>>
>>CLEANMARKER node found at 0x000d0000, not first node in block (0x000c0000)
>>
>>Empty flash at 0x000efffc ends at 0x000f0000
>>
>>CLEANMARKER node found at 0x000f0000, not first node in block (0x000e0000)
>>
>>Empty flash at 0x0010fffc ends at 0x00110000
>>
>>CLEANMARKER node found at 0x00110000, not first node in block (0x00100000)
>>
>>Empty flash at 0x0012fffc ends at 0x00130000
>>
>>CLEANMARKER node found at 0x00130000, not first node in block (0x00120000)
>>
>>Empty flash at 0x0014fffc ends at 0x00150000
>>
>>CLEANMARKER node found at 0x00150000, not first node in block (0x00140000)
>>
>>Empty flash at 0x0016fffc ends at 0x00170000
>>
>>CLEANMARKER node found at 0x00170000, not first node in block (0x00160000)
>>
>>Empty flash at 0x0018fffc ends at 0x00190000
>>
>>CLEANMARKER node found at 0x00190000, not first node in block (0x00180000)
>>
>>Empty flash at 0x001afffc ends at 0x001b0000
>>
>>CLEANMARKER node found at 0x001b0000, not first node in block (0x001a0000)
>>
>>Empty flash at 0x001cfffc ends at 0x001d0000
>>
>>CLEANMARKER node found at 0x001d0000, not first node in block (0x001c0000)
>>
>>Empty flash at 0x001efffc ends at 0x001f0000
>>
>>CLEANMARKER node found at 0x001f0000, not first node in block (0x001e0000)
>>
>>Empty flash at 0x0020fffc ends at 0x00210000
>>
>>CLEANMARKER node found at 0x00210000, not first node in block (0x00200000)
>>
>>Empty flash at 0x0022fffc ends at 0x00230000
>>
>>CLEANMARKER node found at 0x00230000, not first node in block (0x00220000)
>>
>>Empty flash at 0x0024fffc ends at 0x00250000
>>
>>CLEANMARKER node found at 0x00250000, not first node in block (0x00240000)
>>
>>Empty flash at 0x0026fffc ends at 0x00270000
>>
>>CLEANMARKER node found at 0x00270000, not first node in block (0x00260000)
>>
>>VFS: Mounted root (jffs2 filesystem).
>>
>>Mounted devfs on /dev
>>
>>Freeing unused kernel memory: 240k init
>>
>>serial console detected. Disabling virtual terminals.
>>
>>init started: BusyBox v0.60.3 (2004.01.09-22:53+0000) multi-call binary
>>
>>Initializing iocspi
>>
>>Warning: loading /lib/modules/iocspim.o will taint the kernel: no license
>>
>>See http://www.tux.org/lkml/#export-tainted for information about
>>tainted modu
>>
>>les
>>
>>iocspi: release_20060418
>>
>>iocspi: major 254.
>>
>>Module iocspim loaded, with warnings
>>
>>Initializing canspi
>>
>>Warning: loading /lib/modules/canspim.o will taint the kernel: no license
>>
>>See http://www.tux.org/lkml/#export-tainted for information about
>>tainted modu
>>
>>les
>>
>>canspi: init_module()
>>
>>canspi: init_module(): sema_init
>>
>>canspi: init_module(): register_chrdev
>>
>>canspi: major 253.
>>
>>canspi: micro_config()
>>
>>canspi: micro_config: PSC request_irq failed (0)
>>
>>canspi: micro_config psc=f0002400 cdm=f0000200 gpio=f0000b00
>>portcfg=10051004
>>
>>Module canspim loaded, with warnings
>>
>>Initializing iocdrv
>>
>>Warning: loading /lib/modules/iocdrvm.o will taint the kernel: no license
>>
>>See http://www.tux.org/lkml/#export-tainted for information about
>>tainted modu
>>
>>les
>>
>>iocdrv: release_20060502
>>
>>iocdrv: major 252.
>>
>>Module iocdrvm loaded, with warnings
>>
>>System initialized
>>
>>MontaVista(R) Linux(R) Professional Edition 3.1
>>
>>cpua login:
>>
>>Any help would be highly appreciated.
>>
>>Thank you,
>>
>>Orges Furxhi
>>
>>------------------------------------------------------------------------
>>
>>_______________________________________________
>>Linuxppc-embedded mailing list
>>Linuxppc-embedded@ozlabs.org
>>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>
>>
>>
^ permalink raw reply
* [RFC] New hcall mechanism Was: [PATCH 0/3] powerpc: Instrument Hypervisor Calls
From: Jimi Xenidis @ 2006-06-14 14:39 UTC (permalink / raw)
To: Mike Kravetz; +Cc: Bryan Rosenburg, linuxppc-dev, Christopher Yeoh
In-Reply-To: <20060614034756.GA6759@monkey.ibm.com>
Looking at this patch set, it reminds me how IMNSHO the plpar calling
mechanism in Linux are a little arcane.
When we were writing "toy" OSes for hypervisors we had the following
assembly:
### NOTE: this code does not accommodate passing args in r11 & r12
(arg 8 and 9),
### and 'in' could be used to streamline the fetching of r11 & r12
from the stack where the ABI has placed them.
#define PAPR(in, out, name, func_code) \
_GLOBAL(name); \
/* profiling code here */ \
std r3,-GPR_WIDTH(r1); \
li r3,func_code; \
HSC; \
/* profiling code here */ \
ld r12,-GPR_WIDTH(r1); \
cmpi 0,r12,0; \
bne ret ## out; /* only store regs if r12 != NULL,
indicating the caller does not care about the return value */ \
b ret0
ret7: std r10, 6 * GPR_WIDTH(r12)
ret6: std r9, 5 * GPR_WIDTH(r12)
ret5: std r8, 4 * GPR_WIDTH(r12)
ret4: std r7, 3 * GPR_WIDTH(r12)
ret3: std r6, 2 * GPR_WIDTH(r12)
ret2: std r5, 1 * GPR_WIDTH(r12)
ret1: std r4, 0 * GPR_WIDTH(r12)
nop
ret0: blr
PAPR(4, 1,papr_enter, H_ENTER)
...
This allowes for the C interface for H_ENTER to be:
long papr_enter(ulong *slot, ulong flags, ulong hpte_group, ulong
hpte_v, ulong hpte_r);
making the call:
ulong slot;
lapr_rc = papr_enter(&slot, flags, hpte_group, hpte_v, hpte_r);
Rather than:
ulong slot, dummy0, dummy1;
lpar_rc = plpar_hcall(H_ENTER, flags, hpte_group, hpte_v, hpte_r,
&slot, &dummy0, &dummy1);
The latter saving pointers to stack variables on the stack before the
call.
A mechanism such as this could also make the profiling far simpler
and efficient as the profiling code get generated by the PAPR() macro
above.
I is also possible to generate the prototypes from the PAPR()
statements above.
Comments welcome?
-JX
On Jun 13, 2006, at 11:47 PM, Mike Kravetz wrote:
> This patch series adds instrumentation to Hypervisor calls. Code and
> ideas were taken from the patch set provided by Christopher Yeoh.
>
> The idea is to put all instrumentation code behind a configuration
> option so that it can easily be added/removed. The instrumentation
> code is kept to a minimum in the hopes that it's impact to performance
> will not be noticed. Statistics are made available via files in
> sysfs.
>
> --
> Mike
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
^ permalink raw reply
* Re: [Alsa-devel] RFC: dma_mmap_coherent() for powerpc/ppc architecture and ALSA?
From: Takashi Iwai @ 2006-06-14 14:42 UTC (permalink / raw)
To: Gerhard Pircher; +Cc: linuxppc-dev, rlrevell, alsa-devel, linux-kernel
In-Reply-To: <20060612144254.305930@gmx.net>
At Mon, 12 Jun 2006 16:42:54 +0200,
Gerhard Pircher wrote:
>
> > > But as far as I understand this would require a rewrite of all the
> > > ALSA drivers (or at least a rewrite of the ALSA's DMA helper
> > > functions).
> >
> > Yes. The change of ALSA side has been also on my tree. But it was
> > still pending since I'm not satisfied with the design yet.
> > If you're interested in it, let me know. I'll post the patch.
>
> Yes, please! Then I can test, if the dma_mmap_coherent() patch works on
> my non cache coherent powerpc machine.
For using dma_mmap_coherent(), the patch below should suffice.
(Also you need to enable HAVE_DMA_MMAP_COHERENT there not only for
ARM.)
> Do you think the DMA Layer/ALSA patches will go upstream in one of
> the next ALSA/Linux kernel versions?
Definitely no 2.6.18 material yet.
Takashi
diff -r 08577d0b45ef sound/core/pcm_native.c
--- a/sound/core/pcm_native.c Tue Jun 13 12:01:14 2006 +0200
+++ b/sound/core/pcm_native.c Wed Jun 14 16:40:32 2006 +0200
@@ -3123,6 +3123,10 @@ static int snd_pcm_mmap_control(struct s
}
#endif /* coherent mmap */
+#if defined(CONFIG_ARM)
+#define HAVE_DMA_MMAP_COHERENT
+#endif
+
/*
* nopage callback for mmapping a RAM page
*/
@@ -3166,6 +3170,14 @@ static struct vm_operations_struct snd_p
.nopage = snd_pcm_mmap_data_nopage,
};
+#ifdef HAVE_DMA_MMAP_COHERENT
+static struct vm_operations_struct snd_pcm_vm_ops_data_one_map =
+{
+ .open = snd_pcm_mmap_data_open,
+ .close = snd_pcm_mmap_data_close,
+};
+#endif
+
/*
* mmap the DMA buffer on RAM
*/
@@ -3175,6 +3187,16 @@ static int snd_pcm_default_mmap(struct s
area->vm_ops = &snd_pcm_vm_ops_data;
area->vm_private_data = substream;
area->vm_flags |= VM_RESERVED;
+#ifdef HAVE_DMA_MMAP_COHERENT
+ if (substream->dma_buffer.dev.type == SNDRV_DMA_TYPE_DEV) {
+ area->vm_ops = &snd_pcm_vm_ops_data_one_map;
+ if (dma_mmap_coherent(substream->dma_buffer.dev.dev, area,
+ substream->runtime->dma_area,
+ substream->runtime->dma_addr,
+ area->vm_end - area->vm_start))
+ return -EAGAIN;
+ }
+#endif
atomic_inc(&substream->mmap_count);
return 0;
}
^ permalink raw reply
* Re: [PATCH 2/3] powerpc: Instrument Hypervisor Calls: add wrappers
From: Nathan Lynch @ 2006-06-14 14:42 UTC (permalink / raw)
To: Mike Kravetz; +Cc: Bryan Rosenburg, linuxppc-dev, Christopher Yeoh
In-Reply-To: <20060614035258.GC6759@monkey.ibm.com>
Mike Kravetz wrote:
> +config HCALL_STATS
> + bool "Hypervisor call instrumentation"
> + depends on PPC_PSERIES
> + help
> + Adds code to keep track of number of hypervisor calls made and
> + the amount of time spent in hypervisor calls.
> +
> + This option will add a small amount of overhead to all hypervisor
> + calls.
Would be good to say how the stats are made available to userspace
here.
> +DEFINE_PER_CPU(struct hcall_stats[MAX_HCALL_OPCODES+1], hcall_stats);
> +
> +static inline void update_stats(unsigned long opcode, unsigned long t_before)
> +{
> + unsigned long op_index= opcode >> 2;
> + struct hcall_stats *hs = &__get_cpu_var(hcall_stats[op_index]);
> +
> + /* racey, but acceptable for non-critical stats */
> + hs->total_time += (mfspr(SPRN_PURR) - t_before);
> + hs->num_calls++;
> +}
> +
> +extern long plpar_hcall_base (unsigned long opcode,
> + unsigned long arg1,
> + unsigned long arg2,
> + unsigned long arg3,
> + unsigned long arg4,
> + unsigned long *out1,
> + unsigned long *out2,
> + unsigned long *out3);
> +
> +long plpar_hcall(unsigned long opcode,
> + unsigned long arg1,
> + unsigned long arg2,
> + unsigned long arg3,
> + unsigned long arg4,
> + unsigned long *out1,
> + unsigned long *out2,
> + unsigned long *out3)
> +{
> + long rc;
> + unsigned long t_before = mfspr(SPRN_PURR);
> +
> + rc = plpar_hcall_base(opcode, arg1, arg2, arg3, arg4, out1, out2, out3);
> +
> + update_stats(opcode, t_before);
> + return rc;
> +}
Without disabling preemption around the mfspr ... update_stats section
in these hcall wrappers, you risk updating the stats on the wrong cpu.
> +struct hcall_stats {
> + unsigned long num_calls;
> + unsigned long total_time;
> +};
A comment explaining the unit of time used for the total_time field
would be nice.
^ permalink raw reply
* RE: OpenFirmware framebuffer
From: Benjamin Herrenschmidt @ 2006-06-14 14:29 UTC (permalink / raw)
To: matt; +Cc: linuxppc-dev, 'Nathan Lynch'
In-Reply-To: <00b601c68fbb$e9c2c570$99dfdfdf@bakuhatsu.net>
On Wed, 2006-06-14 at 09:07 -0500, Matt Sealey wrote:
> > Send us a copy of your dmesg log. Also, does the pegasos
> > firmware creates a "display" node in OF with the right type
> > and properties ?
>
> dmesg log might be a bit clumsy to get but I will try.
>
> Please tell me what the display node should have? I can check that. I
> am curious though as it does seem to have worked.. it uses the mode I
> set in firmware, cleans the screen and prints a message to display..
> just not MUCH of a message. With previous "broken" firmware and kernels
> I would get a garbage screen with the chrp_boot messages on it, but
> yesterday this new message (welcome to Linux.. MSR, HID0 printout) was
> a welcome change, but.. not a console so much as "not a blank screen".
>
> dmws2: the current released firmware doesn't. But I get to test out all
> these new broken features.. :3
Better, send me a firmware image and I'll check what's up on my
pegasos :)
Ben.
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox