Chris, I just committed a first working kernel module ...
-------- Forwarded Message --------
From: Rick Scott <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: [Xmblackberry-devel] XmBlackBerry/kernel COPYING, NONE, 1.1
Makefile, NONE, 1.1 README, NONE, 1.1 charge.c, NONE, 1.1 charge.h,
NONE, 1.1 config.h, NONE, 1.1 identity.txt, NONE, 1.1 init.c, NONE, 1.1
util.c, NONE, 1.1 util.h, NONE, 1.1
Date: Sun, 19 Oct 2008 02:18:48 +0000
Update of /cvsroot/xmblackberry/XmBlackBerry/kernel
In directory fdv4jf1.ch3.sourceforge.com:/tmp/cvs-serv6361/kernel
Added Files:
COPYING Makefile README charge.c charge.h config.h
identity.txt init.c util.c util.h
Log Message:
Here it is, the kernel driver. If you are scared to death about getting a
system panic don't even attempt to use this!!!!!
It should build with a simple make. I don't recommend a "make install" yet.
Use it with "insmod ./blackberry.ko". Remove it with "rmmod ./blackberry.ko".
When a blackberry is plugged in, that it recognizes, a /dev/bbdesktop device
node will be created. This can be used the same way as a serial or bluetooth
device with XmBlackBerry, "./XmBlackBerry -device /dev/bbdesktop0".
There are a couple of parameters:
debug 0 is the default 9 is extremely verbose. 1 currently shows all of the
usb packets.
num_devices defaults to 2. If you are going to use more than 2 blackberrys
you need to increase this. If you want to use more than 2 without changing
this you have to rmmod the module before the 3rd one can be used. This is
so the first blackberry plugged in will always be /dev/bbdesktop0, the
second /dev/bbdesktop1.
Everything seems to work well with my Fedora Core 4 system, some of the work
was done with CentOS 5.2, different tty driver API between these 2 :( I haven't
noticed any conflicts with bcharge, usb_storage, or anything else for that
matter. I've used it with everything in the identity.txt file, namely 6200,
7100, 8700, and 8800. It only does the "RIM Desktop" interface (okay, bad word,
since a bunch of stuff is on the same "usb interface" ... let's go with
protocol). The modem stuff should be a little simpler, but some use separate
endpoints, and some multiplex it with the desktop, and other, stuff.
The only outstanding issue is with password enabled devices. The serial
protocol prompts for the passwords on the device, the usb protocol handles
the password. Not sure how to handle this yet, linking the kernel module with
openssl isn't an option :(
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Xmblackberry-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xmblackberry-devel
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel
