I just read on the Portal that there has been a generic NTFS driver created that should work on any ARM device with fuse.ko found here
I tried compiling it on my machine, but I think my compiler must be broken, because it choked almost instantaneously (not the first time).
Has anyone managed to compile it for either HC or ICS?
2.6.39.4 kernel modules
Hey there,
I've posted a bunch of kernel modules for ICS (kernel version 2.6.39.4) here (including fuse and ntfs):
forum.xda-developers.com/showthread.php?t=1870077
agc93 said:
I just read on the Portal that there has been a generic NTFS driver created that should work on any ARM device with fuse.ko found here
I tried compiling it on my machine, but I think my compiler must be broken, because it choked almost instantaneously (not the first time).
Has anyone managed to compile it for either HC or ICS?
Click to expand...
Click to collapse
Cheers mate.
I'd totally forgotten about this, even though I fixed my compiler weeks ago
Related
I would like to post a general question about kernel development!
Background:
I've started to look into what it take so to develop a kernel of my own, and I'm guessing its no small undertaking even though everything is linux based... which means all the source exists already. I'm learning linux is awesome in that respect.
Question:
Any reason I can't use google's NDK to do development? I've learned it has the necessary cross compiler for the arm... or at least I think it does.
Ok, let me re-word the question.
I downloaded the kernel source from htc for the thunderbolt. The first thing I did was attempt to compile the source on my Ubuntu computer. After setting up the .config file for the thunderbolt, I soon found I needed an arm cross compiler. I also found NDK includes an arm cross compiler.
I downloaded it, modified the Makefile (I know... there are better ways instead of modifying the Makefile) to point to the NDK cross compiler and it compiled.
My question is... is there any reason I can't use the files that resulted (zImage --> boot.img) on my thunderbolt? Just trying to learn. Should I post this somewhere else?
toymachine115 said:
Ok, let me re-word the question.
I downloaded the kernel source from htc for the thunderbolt. The first thing I did was attempt to compile the source on my Ubuntu computer. After setting up the .config file for the thunderbolt, I soon found I needed an arm cross compiler. I also found NDK includes an arm cross compiler.
I downloaded it, modified the Makefile (I know... there are better ways instead of modifying the Makefile) to point to the NDK cross compiler and it compiled.
My question is... is there any reason I can't use the files that resulted (zImage --> boot.img) on my thunderbolt? Just trying to learn. Should I post this somewhere else?
Click to expand...
Click to collapse
Any ARM toolchain should work, though the android NDK is not always the easiest one to use. Best way to see if you compiled it correctly is to test it of course. Back up your current phone state first of course.
Thanks! I'll attempt it.
Main thing I was going for was to avoid the NO do not use the NDK cross-compiler... so looks like it is ok.
I've had a search and a look around but can't see anything specific enough to answer this.
I have read that the SGS2 uses the new BCM4330 chipset for it's WiFi-N support.
It looks to me that for existing kernels they are using either the existing kernel support or possibly the b43 driver.
I need to find out, and while I have compiled custom kernels in nix in the past, I have never done so in Android, so I'm a little out of my comfort zone here.
I want to compile a kernel where the WiFI driver will support monitor mode, ideally it would be the CM7 kernel with just this extra functionality added, however a number of the tools that I would use to identify the existing configuration do not seem to be available in the standard CM7 build (lspci being one).
I don't want to frack around too much without having read up first so could anyone point me at a good guide for creating my own Android Kernel, even better if the guide was specific to the CM7 version.
Lastly I mostly run a Fedora environment, however the bits I have read seem to suggest a number of tools are only available in a Ubuntu guise (heimdall springs to mind and while I'm sure it's possible to recreate it for Fedora I'm trying to reduce the number of dependencies I'll have to recreate as much as possible). Therefore can I get some advice regarding the least complicated way to generate an Android build environment in Linux.
Thanks
For kernel compilation on android, you can check the several repositories there are for the several kernels. Depending on each kernel/repository/user, you can find a predefined .config inside them, so you can get the basic configuration to compile the kernel, don't know if CM7 has it in its repository...
As for the enviorment, I haven't tried compiling a kernel, but I did compile some ROM on Gentoo Linux, so I suppose it could also be done in Fedora without many problems. The main thing about using Ubuntu is that is very extended, so they're using it as main Linux base, but that doesn't mean it can't be done in other linux distros. You can check CM7 wiki for building from source to install the required packages for your enviorment. In my case I cross checked the Ubuntu packages with Gentoo to install gentoo's version of that packages/tools to be able to compile without problems.
Also in the case of building kernels, you need a toolchain to be able to compile, but there are several webs/tutorials with info on how to use that.
EDIT: You have a complete tutorial for CM7 in their wiki with the needed packages for both Debian and Red Hat based distributions...
Very useful, thanks for the info.
Very useful info.
Hi,
I'm interested in compiling a custom kernel to support wifi monitor mode, but I read in a previous post that it can be a hardware limitation which makes it impossible to use monitor mode. Can anyone confirm that? Maybe a statement/answer from Broadcom?
I'm just asking it because I don't want to start playing with kernel compilation and driver hacking if it can't be done because of some missing code on the chipset or something.
Thanks.
kepten said:
Can anyone confirm that? Maybe a statement/answer from Broadcom?
Click to expand...
Click to collapse
I doubt Broadcom will answer that, but you can try to search the chipset info in Broadcom's web and see if its supported. Also you can check kernel modules if they can compile against that version.
AzureusPT said:
I doubt Broadcom will answer that, but you can try to search the chipset info in Broadcom's web and see if its supported. Also you can check kernel modules if they can compile against that version.
Click to expand...
Click to collapse
Well, Broadcom's website says nothing about monitor mode but I've found a driver (https:// github.com/cyanogen/galaxy-2636/blob/ics/drivers/net/wireless/bcm4330/src/include/wlioctl.h#L1153) which at least mentions it. This is for Galaxy Tab 10.1 which has the same chipset so maybe someone with a Tab 10.1 could verify if monitor mode works with that kernel/driver? ??
I'm trying to get together all the files I need to have a go at getting a DVB-T tuner working with the 3D - I have all the DVB-T modules, but for a lower kernel revision, and from what I've read they probably wont work with this kernel.
I'm really not looking forward to compiling these myself as I use Windows 7 and am aware that there are issues with compiling Linux on a Windows system and being new to Android/Linux cross compiling I could cause myself more problems than I solve.
So the question is, has anyone got info on a repository for these modules compiled for ICS at our kernel revision?
Hi guys!
I hope I finally get a decend answere here... seems like german forums are of no use for such kind of questions
Here is my issue:
I got a wacom graphic tablett wich I want to use on my Android Tablet PC. Of course Android hasn't got a working driver for it, so thats why I want to install an opensource linux driver. So my first question is, if this might be possible. The linux driver is made for a 2.6 Kernel which of course is not complete the same as my 2.6 android Kernel, but are they similar enough to at least give it a try?
And I got an other question: A grafic tablett is you know... nothing else as a weird mouse so am I might be able to tell Android that it shoud use a simple mouse driver for the graphic tablett? Because my mouse is running well on it.
So thats it. Any help is appreciated!
Got any news on that? I'm facing a similar issue, but still haven't found an answer.
Doesn't work like that. Android won't know what to do with the driver or the device.
mc.escher said:
Got any news on that? I'm facing a similar issue, but still haven't found an answer.
Click to expand...
Click to collapse
You can't use the same PC drivers, because they are developed for a different platform (i386 or amd64 on PC, ARM on mobile devices).
RoberGalarga said:
You can't use the same PC drivers, because they are developed for a different platform (i386 or amd64 on PC, ARM on mobile devices).
Click to expand...
Click to collapse
063_XOBX said:
Doesn't work like that. Android won't know what to do with the driver or the device.
Click to expand...
Click to collapse
I have the linux drivers for the chipset of my usb-ethernet converter (MCS 7830).
I was thinking about cross compiling them as a module, with the arm compiler that comes with Android NDK, and then give an "insmod" on adb shell. Is it possible? Have you guys ever heard about something like that?
Thank you!
mc.escher said:
I have the linux drivers for the chipset of my usb-ethernet converter (MCS 7830).
I was thinking about cross compiling them as a module, with the arm compiler that comes with Android NDK, and then give an "insmod" on adb shell. Is it possible? Have you guys ever heard about something like that?
Thank you!
Click to expand...
Click to collapse
Try it, but I think it's not easy as that (problems with libs, memory locations or stuff like that).
RoberGalarga said:
Try it, but I think it's not easy as that (problems with libs, memory locations or stuff like that).
Click to expand...
Click to collapse
I actually did it today! Dude, that thing was tough for me, I'm such a noob on compiling custom kernels and stuff like that.
But it's not exactly using a linux driver on an android. I found a custom kernel that had the needed drivers (I'm not sure if those were the same linux drivers, or if they were adapted to android), but they weren't added to the kernel image as default. So, I compiled them as modules. I had to set a few variables on the .config file as "m", some of them weren't even there, and I had to figure out what were missing and paste them out.
Finally, after several hours struggling with compilers, makefiles and .configs, I did an "insmod mii.ko", "insmod usbnet.ko" and "insmod mcs7830.ko" and everything went fine, and now I have my usb-ethernet dongle working on my samsung galaxy s2 i9100.
I'll try to write a tutorial with all the steps I took until I reached success.
mc.escher said:
I actually did it today! Dude, that thing was tough for me, I'm such a noob on compiling custom kernels and stuff like that.
But it's not exactly using a linux driver on an android. I found a custom kernel that had the needed drivers (I'm not sure if those were the same linux drivers, or if they were adapted to android), but they weren't added to the kernel image as default. So, I compiled them as modules. I had to set a few variables on the .config file as "m", some of them weren't even there, and I had to figure out what were missing and paste them out.
Finally, after several hours struggling with compilers, makefiles and .configs, I did an "insmod mii.ko", "insmod usbnet.ko" and "insmod mcs7830.ko" and everything went fine, and now I have my usb-ethernet dongle working on my samsung galaxy s2 i9100.
I'll try to write a tutorial with all the steps I took until I reached success.
Click to expand...
Click to collapse
Dude have you written the tutorial yet?
Hi everyone!
I have a rooted Galaxy S2 i9100 with ICS 4.0.3
Kernel version is 3.0.31-Siyah-s2-v5.0.1+
I just bought a USB-ethernet adapter, and I'm trying to make it work with my i9100.
The chipset on the adapter is a MCS7830, and I found the drivers for Linux kernel 3.x here:
( asix.com.tw / FrootAttach / driver / MCS783x_Linux_driver_v1.11.zip ) - sorry, I can't post links yet.
When I plug the adapter, the android recognizes it, but it doesn't generate an eth0 nor an usb0 connection on netcfg.
I've found on other threads that it could be a driver fault, and a possible solution would be to build these drivers as a kernel module. Is it possible? I'm trying to build a .ko module for it, but I still can't even handle the "hello_world.ko". I'd really appreciate and be thankful if someone could build a .ko for this driver.
Thank you in advance!
Any ideas?
Just to let you guys know, I just did it. I'll try to post a tutorial as soon as possible to help people that might have faced the same issues with similar dongles.
I recompiled the needed drivers as modules ("make modules") with the ARM compiler that comes with the Android NDK;
Set up the .config and Makefile from SiyahKernel 5.0.1+ with some values;
Pushed the modules to my phone and loaded manually the modules.
Siyah Kernel actually has many drivers (including other usb-ethernet chipsets)! Learning how to compile specific drivers as modules might be useful for many people.
nice to know that there is someone how found a solution. please post a detailed tutorial! I am desperately trying to get this work for 3 weeks now, without success. i ordered different usb-ethernet-adapters from amazon, i have just 5 days left to send them all back...
a tutorial would be very helpful! btw: does your solution only work with the siyah-kernel or with every kernel on a rooted phone?
thanx in advance, alex
mc.escher said:
Just to let you guys know, I just did it. I'll try to post a tutorial as soon as possible to help people that might have faced the same issues with similar dongles.
I recompiled the needed drivers as modules ("make modules") with the ARM compiler that comes with the Android NDK;
Set up the .config and Makefile from SiyahKernel 5.0.1+ with some values;
Pushed the modules to my phone and loaded manually the modules.
Siyah Kernel actually has many drivers (including other usb-ethernet chipsets)! Learning how to compile specific drivers as modules might be useful for many people.
Click to expand...
Click to collapse