Hi, I have no clues about cross compiling and bootloaders other than grub (ok, maybe lilo) but if you want to determine if that device is seen as a storage device why don't you just plug it in and have a look at dmesg? when I plug a usb key on my machine i see something like this: [ 1647.577443] usb 2-1:1.0: uevent [ 1647.577488] usb-storage 2-1:1.0: usb_probe_interface [ 1647.577500] usb-storage 2-1:1.0: usb_probe_interface - got id [ 1647.577618] scsi5 : SCSI emulation for USB Mass Storage devices [ 1647.577848] usb-storage: device found at 3 [ 1647.577853] usb-storage: waiting for device to settle before scanning [ 1647.577966] drivers/usb/core/inode.c: creating file '003' [ 1652.579409] scsi 5:0:0:0: Direct-Access USB DISK 2.0 1219 PQ: 0 ANSI: 0 CCS [ 1652.581857] sd 5:0:0:0: [sdb] 15663104 512-byte hardware sectors: (8.01 GB/7.46 GiB) [ 1652.592206] sd 5:0:0:0: [sdb] Write Protect is off [ 1652.592214] sd 5:0:0:0: [sdb] Mode Sense: 43 00 00 00 [ 1652.592220] sd 5:0:0:0: [sdb] Assuming drive cache: write through [ 1652.595359] sd 5:0:0:0: [sdb] 15663104 512-byte hardware sectors: (8.01 GB/7.46 GiB) [ 1652.596203] sd 5:0:0:0: [sdb] Write Protect is off [ 1652.596210] sd 5:0:0:0: [sdb] Mode Sense: 43 00 00 00 [ 1652.596215] sd 5:0:0:0: [sdb] Assuming drive cache: write through [ 1652.596221] sdb: sdb1 [ 1652.646484] sd 5:0:0:0: [sdb] Attached SCSI removable disk [ 1652.646551] sd 5:0:0:0: Attached scsi generic sg2 type 0 [ 1652.661531] usb-storage: device scan complete [ 1652.663087] usb 2-1:1.0: uevent [ 1652.663212] usb 2-1: uevent
this tells me it's a storage device and the associated evice file is /dev/sdb1 so i know where to find it... HTH Davide 2009/6/30 Stroller <strol...@stellar.eclipse.co.uk>: > > On 30 Jun 2009, at 11:21, dhk wrote: >>> >>> ... >>> Finally, can you even install Linux on this scanner? Chances are its >>> processor is ARM - Linux will run on that architecture, but you won't be >>> able to chroot in from your x86 box & install GRUB. >>> >>> Chances are that this scanner is some kind of rebadged HP iPaq or >>> something, onto which Linux has been / can be cludged onto, but you seem >>> to be making a lot of assumptions ahead of time. >>> >> >> I done have a Windows box so I don't know how it looks on that. >> However, I already build the arm cross compiler and have a kernel to >> install on it, the only thing is I don't know how to reach it. Now I >> just want to know how to get the kernel to the device. This may be a >> bigger project than I thought. > > Having managed to cross-compile the kernel is a pretty good start. I > couldn't do that much. > > But you need to determine stuff like how the bootloader works on this > device. > > As I said, chances are that the device is not completely unique. If it is > simply a rebadged HP iPaq or something then efforts (at the very least) to > install Linux on it will surely be documented. First thing to do is learn > all you can about the hardware. > > Stroller. > > >
