Database Users

bnep.ko kernel module

Hello
Can someone point me in the right direction to learn how to compile a kernel module for the atrix?
I would like to use bluetooth PAN to tether my tablet to my atrix but can't do it without the bnep.ko module.
or if someone who is already set up for it and feeling kind wants to compile it for me (ATT Gingerbread 2.3.4 kernel), that would be great too

faux123 kernels already have BNEP support built-in, check them out.

awesome! thank you. i tried looking in the changelog and did not see it.
I appreciate you pointing me in that direction

I just got version 1.9 of faux and unfortunately there is no bnep0 interface found nor any bnep.ko file for me to run with insmod to enable it.
Any other ideas?

The interface will appear and everything will work when you actually pair with a device and connect it to your phone. At least it works that way on CM7

[Q] help build cp210x.ko on Iconia A500 3.2.1

Hi,
I really need the cp210x.ko module, but I couldn't successfully build it properly for my Iconia A500 with 3.2.1 and 2.6.36.3+ kernel.. I get the following when I tried insmod my cp210x.ko build using ubuntu cross compiler approach:
cp210x: version magic '2.6.36.3+ preempt mod_unload ARMv5 ' should be '2.6.36.3+ SMP preempt mod_unload ARMv7 '
A little search showed that I need to build it in ARMv7, and need to set the kernel config to build SMP kernel. In this thread I saw a few modules offered but couldn't post reply as a new xda-developers user, so I post here. My A500 has already been rooted via the su (version 3) method posted few days ago.
Please help me build the cp201x.ko module - I am kinda stuck..
Bill

Bill,
Might I suggest you look at loading one of the many custom ROM's that will have what you want? If you are rooted, then install CWM (ACER Recovery from the marketplace) which should allow you to load custom ROM's. In order to load the cp201x.ko module you'd have to recompile the kernel and people doing this type of work normally are building custom ROM's.
Anyway, just my 2¢

Thanks for the advice. I am testing Thor ROM at the moment. Cool..
From what I can read and see within various ROMs /system/lib/modules, very few (out of total possible) kernel modules made it to these custom ROMs - mostly to get game controller to work, extra filesystems, or networking protocols. USB-to-serial modules are rare and certainly my search didn't turn up cp210x.
Cross-compiling the kernel source on Gentoo is mentioned to be better supported then ubuntu, due to its crossdev toolkit, as I'm trying to figure out how to specify target ARMv7 instead of ARMv5 I'm defaulting to when cross compiling from Ubuntu's arm-linux-gnueabi-*
I'm wondering if various nice ROM cooks have releases of their modified kernel source - or might be willing to help me build the just the cp210x as a .ko module, e.g. in the .config, "CONFIG_USB_SERIAL_CP210X=m" - I've found a post few months ago where a successful build and insertion of cp210x module was done but he had some problems when initiating communication on it - I fear the worst but hope for the best, and would like to try that myself as I've successfully talked to my device through the cp210x module on Linux.
Or, if any tips on how to build kernel (just the modules really) properly e.g. As Thor's ROM version number hints at need for some custom and virtualized build environment, I'm looking for the quick and dirty solution if cooking ROMs/kernel/ko's has steep learning curve..
Any help much appreciated!
Bill

It looks like I was speeding down the the wrong track last few days
Apparently the /proc/config.z copied off the a500 device was missing something - and how strange that is - so I had to enable SMP and choose Tegra 2 ARM processor using "make menuconfig" to get the vermagic on the build module (e.g. modinfo after successful make modules) to show ARMv7 and SMP, build from my Ubuntu cross-compiling setup. I haven't tested this new cp210x.ko on a500 yet (as it's currently running one of the customized ROMs that has different EXTRAVERSION/vermagic to the stock Acer kernel source version 2.6.36.3 that I'm based on.
I think it'd be really wonderful if various Android kernel and kernel module makers release their kernel config, sync'ed to each ROM or kernel release, so people like me may independently build special purpose kernel modules with more efficiency and accuracy (to target their customized kernel), and we can recontribute back to to a growing list of tested and working modules for corresponding devices.
Bill

Hmm... Silly. It looks like Thor's ROM already has cp210x build-in, not as a loadable module but compiled in. My device is reported to attach to ttyUSB0! How nice
Thanks!
Bill

For those who are interested, the cp210x.ko module build using latest mentioned approach, e.g. modified kernel config.z, generate module that appear to insert correctly into lightspeed and taboonay roms (neither has this USB-to-serial module) - with a little modification of the EXTRAVERSION variable in the Makefile.
Bill

CP210x and GT-P7500
Has anyone got CP210x module working with Samsung Tab GT-P7500? My problem is that the connected USB-device doesn't create node dev/ttyUSB*. I have spent lot of time trying to figure this one out.
I have tried 1) Manually compiling the linux kernel that has cp210x support as a module. After compiling the module I tried insmoding the cp210x.ko to a running kernel, but even though it seemed to load and unload all right, it did not give me the wanted results. It does not create device node /dev/ttyUSB*. I have also tried modifying ueventd.rc for adding this row, but I am guessing it is only relevant for permissions after the node is created.
Also 2) loading cyanogenmod 10 (which should have cp210x support) to tablet but it doesnot create the desired /dev/ttyUSB* node. I can see device file under dev/bus/usb/001/ but the node does not exist.
I am going to try making needed files for building custom kernel and inserting to tablet. However, I have 0 experience on this, I think it can be tough one.
Any help would be welcome, thanks.

[Q] Adding Android Open Accessory (AOA) protocol to defy (CM10)

Hi all!
I will try to get the Android Open Accessory (AOA) protocol into our defy/defy+.
Anybody else working on this topic?
Atm I just added the android.hardware.usb.accessory.xml file to /etc/permissions and the com.android.future.usb.accessory.jar to /system/framework (jar taken from the droid sdk API16, my fw is latest quarx CM10).
Right now I can install f.w. the ADK2012 app. So I may on the right way... but I guess that is not all the work... does anybody know if we need to add some kernel modules f.e.?
[Edit] btw... looks like we just need to add a new f_accessory.o to our usb gadget... f.e. see https://www.codeaurora.org/gitweb/q...in;h=5d9d8625e39f815673dedea353f39edccabb1fac
Best regards, Stephan

Like to know this to. If quarx managed to give us sub host, I might be able to use my duomilanove board...
Aren't there other projects for the ADK that doesn't use the protocols?

Please ask all questions in the Q&A section. Thread moved there.

Ok... I gave it a short try with the patch and quarx's linux-2.6.32 but it failed during the compiliation... but meanwhile I noticed that quarx is working on linux-3.0.8 (see its repo in github). There we have our accessory...
So I would say stay tuned for a while and let's if quarx may got this newer kernel working with our defy...

You can find all the steps needed to patch it here:
https://github.com/ezterry/manifest-gingerbread-DS/issues/32
They're saying everywere that you need 2.6.35+ kernel (don't know if it really is mandatory, kernel in the link is 2.6.34)
A kernel with the same chipset that has it enabled can be found here:
https://github.com/XDA-Bam/samsung_kernel_latona_GB
Apparently, you need to enable it in the kernel (config), add the libs to the kernel (driver/usb/f_accesory and include/linux/f_.accesory), add the lib in the framework (might be included from CM side already??), hope it will work (or debug why not).
---------- Post added at 01:21 AM ---------- Previous post was at 01:06 AM ----------
It seems that the files are indeed in the 3.0 kernel.
I already ordered a USB-host shield for my arduino a week ago, I'll try and compile a kernel with it ones it comes in the mail.
Edit:
Tried the changes I listed, will build it tomorrow (or so). Maybe then my shield might arrive to (hate waiting, stupid holidays.. )
Any place to upload it when it works?

Got something build, but it didn't include the /system/framework/com.android.future.usb.accessory.jar and got bootloop without (cause I added the /etc/permision/something_with_usb_accesory.something
Pushed the jar with adb from bootmenu (from another CM rom).
Don't have the usb_shield yet, so can't really test. Will try and install an usb_accessory app. Does someone want the build to try?
Ok, the app fails to launch.

Ok, my repo's:
Kernel: https://github.com/labsin/jordan-kernel/commits/2.6.32
Device: https://github.com/labsin/android_device_moto_jordan-common/commits/jb_2ndboot
But doesn't work. The library isn't build (in framework/base).
And it also doesn't build in the kernel... :/
Anyone??

Might it be possible to check the driver?
Edit: Found it.
It seems to many commits need to be merged in. Can't seem to find a kernel that's not based on the nexus line that has it.

If anyone is still interested in this, I managed to make an Arduino Mega ADK board with the DemoKit application work in accessory mode on my Defy
Quarx backported the USB gadget driver from 3.0.8 kernel into his 2.6.32 based kernel already a while ago. All that was still missing was the accessory configuration in init.usb.rc and the .jar and .xml files. Quarx has already merged my pull request, so in the next CM10.1 nightly with 2.6.32 kernel, USB accessory mode should work out of the box

Thnx. Already saw this actually

Stock /proc/config.gz for GT-P5100

My device a Samsung Galaxy Tab 2 10.1 (GT-P5100) does not have a /proc/config.gz. I already rooted my device and searched for it on it's filesystem using root explorer, but no luck. I also tried to extract config.gz from boot.img, also no luck.
From were do I obtain /proc/config.gz file now? Or can anyone upload it for a GT-P5100 with 16GB + 3G and WiFi?
My final approch is to build a custom Kernel with the UDLFD driver enabled to use my DisplayLink device connected to my full HD TV as monitor
My DisplayLink works fine with a OpenWrt router but I like to use it with my tablet.

Samsung doesn't enable that option in the kernel on any device. If you read the readme included in the kernel source though, you will find out what defconfig file to use, which is packaged with the kernel source.

I'm not aware of this
Then I'll digg into the Kernel source and look for the default Samsungs config. Thanks for the hint
From the README_Kernel file:
* defconfig_file
- android_espresso10_omap4430_r02_user_defconfig : GT-P5100
Click to expand...
Click to collapse

Sero 7 Pro Modifying ROM for ad hoc Wi-Fi

I am posting here asking for help, assistance, coaching.
It seems to me that I have all the pieces to properly modify the Sero 7 Pro ROM to accept ad hoc Wi-Fi connections. I've spent several days trying to find a simple step-by-step guide for applying github patches to existing kernels and flashable ROM. I have come to believe that no such simple guide/aid exists because the process itself appears to be complex.
The Nexus 7 CyanogenMod has been successfully modified for ad hoc Wi-Fi. My research indicates that the Sero 7 and the Nexus 7 are similar enough that the same patches should be able to be applied to the Sero 7 ROM. The Nexus 7 and Sero 7 both:
Use Android Jelly Bean 4.2.X
Have the same processor, 1.3GHz NVIDIA Tegra 3
Use the same Wi-Fi Chip, Broadcom BCM4330
Kernels use the same Driver, Broadcom bcmdhd Version 5.90.195.104
What I have is the kernel source
http://hisense-usa.com/support/firmware/Sero%207%20Pro_kernel_opensource_us.tar.gz
The full Stock ROM, latest version
https://skydrive.live.com/redir?resid=F7DECBA5BB726100%21108
Patches applied to Nexus 7 CyanogenMod ROM with detailed discussion
http://www.thinktube.com/android-tech/46-android-wifi-ibss
Briefly summarizing the discussion and code contained in the above Thinktube webpage:
The Kernel is patched making changes to the bcmdhd Wi-Fi driver
The ROM is patched making changes
to the wpa_supplicant
a few additions to the Android framework and
some changes to the Settings App
So in concept it seems pretty straightforward. Where I am struggling is the whole github process of applying the patch to the Kernel source. Then compiling the modified Kernel source. And applying the remaining patches to the ROM with the newly modified Kernel.
I need someone willing to work with me on the github piece. Or alternately coach me through that process.

So the resounding lack of response tells me either I've posted on the wrong forum or it is indeed as complex and cumbersome as I suspected.
But I may have figured out how to accomplish it myself. I have NOT figured out the github process. But I do know a little Linux and do run a virtual Ubuntu machine.
So I :
1. manually modified the Broadcom bcmdhd in the kernel source line by line.
2. swapped the wpa_supplicant file in the Sero7 stock ROM with the one from the Nexus 7 CyanogenMod ROM.
3. extracted the needed sero7_defconfig and initramfs.cpio.gz files
4. compiled the modified kernel source code and created a new boot.img
5. inserted the new boot.img to complete the modification of the Stock ROM
And if this all works, I’ll post my fix in a new thread, perhaps “Sero 7 Pro hoc Wi-Fi Fix”

wpa_supplicant
bardell3600 said:
So the resounding lack of response tells me either I've posted on the wrong forum or it is indeed as complex and cumbersome as I suspected.
But I may have figured out how to accomplish it myself. I have NOT figured out the github process. But I do know a little Linux and do run a virtual Ubuntu machine.
So I :
1. manually modified the Broadcom bcmdhd in the kernel source line by line.
2. swapped the wpa_supplicant file in the Sero7 stock ROM with the one from the Nexus 7 CyanogenMod ROM.
3. extracted the needed sero7_defconfig and initramfs.cpio.gz files
4. compiled the modified kernel source code and created a new boot.img
5. inserted the new boot.img to complete the modification of the Stock ROM
And if this all works, I’ll post my fix in a new thread, perhaps “Sero 7 Pro hoc Wi-Fi Fix”
Click to expand...
Click to collapse
Oh boy! I've been waiting to hear if someone got the ad-hoc going on the Sero 7 Pro. I've posted asking for help doing this too but never seemed to get a working answer. Did you get yours working and if so could you please post the wpa_supplicant file for the Sero? I would sure like to wifi tether to the Sero. It's the only device I have that doesn't see my phone's wifi.
Thanks a bunch!
Bob