I did try to use the Makefile included in magoroku's code to generate
the .ko file, but that didn't work.
So then I modified his Makefile to the following:
obj-m := displaylink.o
displaylink-y := displaylink-main.o displaylink-usb.o displaylink-
blit.o displaylink-fb.o displaylink-ioctl.o
all:
$(MAKE) -C /lib/modules/`uname -r`/build SUBDIRS=$(PWD) modules
clean:
rm -f *.o *.ko *.mod.* .*.cmd Module.symvers
rm -rf .tmp_versions
That worked in the sense that it made a .ko file. So then I copied
that to my Windows system (I'm running Ubuntu in a virtual machine and
I haven't gotten USB devices to work properly yet). Then I used adb
to push the .ko file onto /system/lib/modules.
After that, I tried to insmod the .ko file and it gave me an EXEC
error failure. I'm not sure if it was built wrong or if I need to
rebuild the whole android source, which is what I am trying right now.
NOTE: this is on a rooted Motorola Droid running 2.1
On Jul 7, 2:26 pm, "Sven Killig" <s...@killig.de> wrote:
> > -----Original Message-----
> > From: android-kernel@googlegroups.com [mailto:android-
> > ker...@googlegroups.com] On Behalf Of Brandon Rosenbaum
> > Sent: Wednesday, July 07, 2010 4:09 PM
> > To: Android Linux Kernel Development
> > Subject: [android-kernel] DisplayLink Android Driver
>
> > The part I am confused about is how to go about adding the driver to
> > my phone. Do I need to download the Android source code, add the
> > driver to that, and then build the whole thing? Or is it possible to
> > just load the driver as a module?
>
> Perhapshttp://sven.killig.de/android/N1/2.2/usb_host
> does help you.
--
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-kernel
