Menu
▾
▴
linuxsh-dev
|
From: Kristoffer E. <kri...@ho...> - 2007-01-11 20:58:53
|
Greetings, Currently "machine" is set to HP6xx and changing it to Jornada6xx would make it more similiar to the Jornada720 line. Im just wondering about one thing. On most PDA's running linux (Jornada7xx and Zaurus for example). They also contain a Hardware line, what exactly is the difference between those lines if any? And how can one create a hardware line for the HP6xx? Best wishes Kristoffer Ericson _________________________________________________________________ Don't just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ |
|
From: Kristoffer E. <kri...@ho...> - 2007-01-13 21:51:30
|
Greetings, We've only recently aquired a working bootloader for CE 2.0 (and most likely CE 1.0) but users are having issues. I've made them test all kernels (2.6.11->2.6.17) and same error has appeard everytime. Suggestions, ideas? Best wishes Kristoffer Ericson Linux version 2.6.16-sh (root@turingbirds) (gcc version 3.4.4) #29 Wed Jan 10 19:48:46 CET 2007 On node 0 totalpages: 4096 DMA zone: 4096 pages, LIFO batch:0 DMA32 zone: 0 pages, LIFO batch:0 Normal zone: 0 pages, LIFO batch:0 HighMem zone: 0 pages, LIFO batch:0 Built 1 zonelists Kernel command line: mem=16M ramdisk_size=8192 ide0=0x1f0,0x3f6,93 ide_setup: 0x1f0,0x3f6,93 ide_init hwif ports: must not be called -- OBSOLETE OPTION, WILL BE REMOVED SOON! PID hash table entries: 128 (order: 7, 2048 bytes) Interval = 55275 Using tmu for system timer Console: colour dummy device 80x25 Dentry cache hash table entires: 4096 (order: 2, 16384 bytes) Inode-cache hash table entries: 2048 (order: 1, 8192 bytes) Memory: 10368k/16386k available (1401k kernel code, 6016k reserved, 194k data, 60k init) Calibrating delay loop... 58.57 BogoMIPS (lpj=292864) Mount-cache hash table entries: 512 CPU: SH7708 checking if image is initramfs...it isn't (no cpio magic); looks like an initrd Freeing initrd memory: 4096k freed NET: Registered protocol family 16 HD64461 configred at 0xb0000000 on irq 36(mapped into 80 to 95) HD64461: enabling PCMCIA devices io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfg registered Console: switching to colour frame buffer device 80x30 fb0: Hitachi HD64461 frame buffer device RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx ide: SuperH generic IDE interface ide-sh: Attempting to register ide2 when only 1 interfaces are available. Probing IDE interface ide0... hda: SanDisk SDCFB-512, CFA DISK drive Probing IDE interface ide1... ide0 at 0x1f0-0x1f7,0x3f6 on irq 93 hda: max request size: 128KiB hda: 1000944 sectors (512MB), w/1KiB Cache, CHS=993/16/63 hda:<4>hda: lost interrupt hda: lost interrupt hda: lost interrupt hda: lost interrupt hda: lost interrupt hda: lost interrupt hda: lost interrupt hda: lost interrupt hda: lost interrupt hda: lost interrupt hda1 HD64461 PCMCIA bridge. hd64461_init(0) hd64461_set_voltage(0, 0, 0) hd64461_set_socket(sock=0, flags=0, csc_mask=80, Vcc=0, Vpp=0, io_irq=0) cscier=08 gcr=18 mice: PS/2 mouse device common for all mice ts: Compaq touchscreen protocol output HP620 matrix scan keyboard registered hd64461 get_status(0) = 0 input: Hitachi scankeyboard as /class/input/input0 input: HP Jornada touchscreen as /class/input/input1 RAMDISK: Compressed image found at block 0 EXT2-fs warning: maximal mount count reached, running e2fsck is recommended VFS: Mounted root (ext2 filesystem). Freeing unused kernel memory: 60k freed Warning: unable to open an initial console. (editor's note: dropped into root@jornada6xx console) _________________________________________________________________ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ |
|
From: Paul M. <le...@li...> - 2007-01-22 00:16:38
|
On Sat, Jan 13, 2007 at 09:51:19PM +0000, Kristoffer Ericson wrote: > We've only recently aquired a working bootloader for CE 2.0 (and most likely > CE 1.0) but users are having issues. I've made them test all kernels > (2.6.11->2.6.17) and same error has appeard everytime. > > Suggestions, ideas? > The IDE registration looks a bit questionable. Either something has grabbed the lower IDs or the MAX_HWIFS need to be bumped up. Consider moving to a newer kernel and going the libata/pata_platform route, though. ide-sh was always a hack. |
|
From: Kristoffer E. <kri...@ho...> - 2007-01-22 21:13:31
|
Greetings, Bumping MAX_HWIFS didnt change anything. Any good way to bugtrack this? Best wishes Kristoffer Ericson >From: Paul Mundt <le...@li...> >To: Kristoffer Ericson <kri...@ho...> >CC: lin...@li... >Subject: Re: "Lost Interrupt" error from HP620 (CE 2.0) users >Date: Mon, 22 Jan 2007 09:15:01 +0900 > >On Sat, Jan 13, 2007 at 09:51:19PM +0000, Kristoffer Ericson wrote: > > We've only recently aquired a working bootloader for CE 2.0 (and most >likely > > CE 1.0) but users are having issues. I've made them test all kernels > > (2.6.11->2.6.17) and same error has appeard everytime. > > > > Suggestions, ideas? > > >The IDE registration looks a bit questionable. Either something has >grabbed the lower IDs or the MAX_HWIFS need to be bumped up. Consider >moving to a newer kernel and going the libata/pata_platform route, >though. ide-sh was always a hack. _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ |
|
From: Paul M. <le...@li...> - 2007-01-11 22:41:51
|
On Thu, Jan 11, 2007 at 08:58:44PM +0000, Kristoffer Ericson wrote: > Currently "machine" is set to HP6xx and changing it to Jornada6xx would make > it more similiar to the Jornada720 line. Im just wondering about one thing. > On most PDA's running linux (Jornada7xx and Zaurus for example). They also > contain a Hardware line, what exactly is the difference between those lines > if any? > cpuinfo is handled by the architecture, the examples you've cited are simply how ARM does it, rather than any real "standard". Things like glibc have a habit of parsing the data from there for various things, and it's generally not worth making changes unless it's clear that there's some point in doing so. > And how can one create a hardware line for the HP6xx? > If you have a use case for why you would need this, it's something that could be considered. "Because ARM does it" is however not a valid use case. Note however that there is no way to differentiate between 620/680/690, since they've all been converged in to a single machine type. |
|
From: Kristoffer E. <kri...@ho...> - 2007-01-11 22:45:33
|
Greetings, My main idea was a quick way to get it working with libopie2. Setting machine into Jornada6xx looks alot nice although it doesnt change anything. As for the Hardware line, I understand what you are saying and considering I've only seen one example where its actually used (Libopie2), I believe its probobly better to adjust their detection mechanism than moving stuff about. Thx for info >From: Paul Mundt <le...@li...> >To: Kristoffer Ericson <kri...@ho...> >CC: lin...@li... >Subject: Re: CPUINFO - Hardware vs Machine >Date: Fri, 12 Jan 2007 07:40:26 +0900 > >On Thu, Jan 11, 2007 at 08:58:44PM +0000, Kristoffer Ericson wrote: > > Currently "machine" is set to HP6xx and changing it to Jornada6xx would >make > > it more similiar to the Jornada720 line. Im just wondering about one >thing. > > On most PDA's running linux (Jornada7xx and Zaurus for example). They >also > > contain a Hardware line, what exactly is the difference between those >lines > > if any? > > >cpuinfo is handled by the architecture, the examples you've cited are >simply how ARM does it, rather than any real "standard". Things like >glibc have a habit of parsing the data from there for various things, and >it's generally not worth making changes unless it's clear that there's >some point in doing so. > > > And how can one create a hardware line for the HP6xx? > > >If you have a use case for why you would need this, it's something that >could be considered. "Because ARM does it" is however not a valid use >case. Note however that there is no way to differentiate between >620/680/690, since they've all been converged in to a single machine >type. _________________________________________________________________ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X