Messages

1

OpenZaurus/Opie/Qtopia / Write My Own Usb Driver

« on: July 03, 2006, 05:30:39 pm »

I have a Zaurus SL-6000, running the factory Sharp ROM. I need to write my own usb device driver or modify the exisiting one. If it turns out that its not possible to do it with the Sharp ROM, I have installed OZ in the past and I don't mind doing it strictly for this purpose. Sorry if this question doesn't really belong in this forum. I wasn't sure where else to post it.  We don't have a "gerneal kernel hacking forum," which would have been the most appropriate one for this post.


Basically, I need to write a small piece of code at the kernel device level, so that the Zaurus can send and receive messages from a computer via the USB interface. Do anyone have any pointers on where I can get started with that?

There is a small usb interface on the Sharp Zaurus docking station, which can be used to transfer files. I was hoping that this should allow me to communicate with the computer.

I went on the Zaurus itself and looked at any modules that deals
with the USB.  There seems to be a couple.

# lsmod | grep usb
prism2_usb             68032   1
p80211                 18880   1  [prism2_usb]
usbdcore               34544   0  [pxa_bi net_fd]
usbdmonitor             5248   0
usb_ohci_tc6393        24544   0
usbcore                52048   1  [prism2_usb usb_ohci_tc6393]
#


My initial reaction was to get the corresponding source code, and then modify it, compile it, and reload the module. Does this seem like to be the correct direction?

Thanks

Mark

2

General Discussion / Help On Understanding The Keyboard Device Driver

« on: April 17, 2006, 11:50:57 am »

The processing I need involves turning off other interrupts, so it probably needs to stay in the kernel.

When i do a dmesg to look at boot messages, I see a line of printouts that seems to pertain to the keyboard

keyboard initilaized.

I greped through the kernel source for this line (it especially helped since "initialized" was misspelled), and grep gave me the following results

root@sparrow:/home/mluk/linuxK# grep -Ri "keyboard initilaized."  *
grep: drivers/char/collie_keyb.c:       printk("keyboard initilaized.\n");
drivers/char/corgi_keyb.c:      printk("keyboard initilaized.\n");
drivers/char/discovery_keyb.c:  printk("keyboard initilaized.\n");
drivers/char/poodle_keyb.c:     printk("keyboard initilaized.\n");
drivers/char/tosa_keyb.c:       printk("keyboard initilaized.\n");


From what I read online, collie, corgi, poodle are codenames for different branches of the Sharp Zaurus development. In particular, it seems like 'tosa' corresponds to SL6000.

So, I'm guessing that tosa_keyb.c is the corresponding driver for my keyboard. Would I be on the right track if I just make my modifications to this file, make a module out of it, and insmod it?

thanks

3

General Discussion / Help On Understanding The Keyboard Device Driver

« on: April 16, 2006, 06:48:29 pm »

Hi,

I need some help on the keyboard device driver of my SL6000 (running the stock SHARP ROM, 2.4.18-rmk7-pxa3-embedix). Any information would be much appreciated.

What I'm trying to do is to modify (or write a new one) the keyboard kernel device driver, so that it would do some addition processing before passing it on to the application. Unfortunately, I'm not sure where to start.

My first question is: how do I identify the current keyboard driver? How do I know if it's in the kernel or its a loadable module? I have the source code of the kernel from the folks where I bought the Zaurus from (http://familiar.sdgsystems.com/pub/zaurus/sl6000/). But how do I know that the source code corresponds to the kernel on my actual Zaurus?



thanks