1 |
Hi, |
2 |
I have no clues about cross compiling and bootloaders other than grub |
3 |
(ok, maybe lilo) but if you want to determine if that device is seen |
4 |
as a storage device why don't you just plug it in and have a look at |
5 |
dmesg? |
6 |
when I plug a usb key on my machine i see something like this: |
7 |
[ 1647.577443] usb 2-1:1.0: uevent |
8 |
[ 1647.577488] usb-storage 2-1:1.0: usb_probe_interface |
9 |
[ 1647.577500] usb-storage 2-1:1.0: usb_probe_interface - got id |
10 |
[ 1647.577618] scsi5 : SCSI emulation for USB Mass Storage devices |
11 |
[ 1647.577848] usb-storage: device found at 3 |
12 |
[ 1647.577853] usb-storage: waiting for device to settle before scanning |
13 |
[ 1647.577966] drivers/usb/core/inode.c: creating file '003' |
14 |
[ 1652.579409] scsi 5:0:0:0: Direct-Access USB DISK 2.0 |
15 |
1219 PQ: 0 ANSI: 0 CCS |
16 |
[ 1652.581857] sd 5:0:0:0: [sdb] 15663104 512-byte hardware sectors: |
17 |
(8.01 GB/7.46 GiB) |
18 |
[ 1652.592206] sd 5:0:0:0: [sdb] Write Protect is off |
19 |
[ 1652.592214] sd 5:0:0:0: [sdb] Mode Sense: 43 00 00 00 |
20 |
[ 1652.592220] sd 5:0:0:0: [sdb] Assuming drive cache: write through |
21 |
[ 1652.595359] sd 5:0:0:0: [sdb] 15663104 512-byte hardware sectors: |
22 |
(8.01 GB/7.46 GiB) |
23 |
[ 1652.596203] sd 5:0:0:0: [sdb] Write Protect is off |
24 |
[ 1652.596210] sd 5:0:0:0: [sdb] Mode Sense: 43 00 00 00 |
25 |
[ 1652.596215] sd 5:0:0:0: [sdb] Assuming drive cache: write through |
26 |
[ 1652.596221] sdb: sdb1 |
27 |
[ 1652.646484] sd 5:0:0:0: [sdb] Attached SCSI removable disk |
28 |
[ 1652.646551] sd 5:0:0:0: Attached scsi generic sg2 type 0 |
29 |
[ 1652.661531] usb-storage: device scan complete |
30 |
[ 1652.663087] usb 2-1:1.0: uevent |
31 |
[ 1652.663212] usb 2-1: uevent |
32 |
|
33 |
this tells me it's a storage device and the associated evice file is |
34 |
/dev/sdb1 so i know where to find it... |
35 |
HTH |
36 |
Davide |
37 |
|
38 |
2009/6/30 Stroller <stroller@××××××××××××××××××.uk>: |
39 |
> |
40 |
> On 30 Jun 2009, at 11:21, dhk wrote: |
41 |
>>> |
42 |
>>> ... |
43 |
>>> Finally, can you even install Linux on this scanner? Chances are its |
44 |
>>> processor is ARM - Linux will run on that architecture, but you won't be |
45 |
>>> able to chroot in from your x86 box & install GRUB. |
46 |
>>> |
47 |
>>> Chances are that this scanner is some kind of rebadged HP iPaq or |
48 |
>>> something, onto which Linux has been / can be cludged onto, but you seem |
49 |
>>> to be making a lot of assumptions ahead of time. |
50 |
>>> |
51 |
>> |
52 |
>> I done have a Windows box so I don't know how it looks on that. |
53 |
>> However, I already build the arm cross compiler and have a kernel to |
54 |
>> install on it, the only thing is I don't know how to reach it. Now I |
55 |
>> just want to know how to get the kernel to the device. This may be a |
56 |
>> bigger project than I thought. |
57 |
> |
58 |
> Having managed to cross-compile the kernel is a pretty good start. I |
59 |
> couldn't do that much. |
60 |
> |
61 |
> But you need to determine stuff like how the bootloader works on this |
62 |
> device. |
63 |
> |
64 |
> As I said, chances are that the device is not completely unique. If it is |
65 |
> simply a rebadged HP iPaq or something then efforts (at the very least) to |
66 |
> install Linux on it will surely be documented. First thing to do is learn |
67 |
> all you can about the hardware. |
68 |
> |
69 |
> Stroller. |
70 |
> |
71 |
> |
72 |
> |