Hi! Has anyone managed to make hardware accelerated encryption working on A101 gen 8?
I don't think so.
BTW if you are interested in archos dev you can if you like also join #openpma on irc.freenode.net or web irc http://www.openaos.org/chat and ask your questions there. Just a note most of them are on european time and sometimes it can take a while before you get an answer.
divx118
If someone is interested in the problem, I should note as a proof of concept, that it's possible to build a working (at least, to some extend) driver for HW accelerated encryption for A101 gen8 (linux with GPL'ed 2.6.29-omap1 kernel).
Some manual work is required to patch and fix sources, but it's relatively easy for an experienced user (sorry, I don't put whole howto here, because am not sure if someone needs it).
Info can be found here:
http://processors.wiki.ti.com/index.php/Cryptography_Users_Guide
https://gstreamer.ti.com/gf/project/arm_crypto/
"Working" here means the driver can run console tests with acceptable results (tested on Debian 6 with 2.6.29-omap1 kernel): http://pastebin.com/Zf63HYcC
Related
Found post about VegaComb being released for Adam on TabletRoms.com. Due to the similarities and the fact that there exists ROMs for G-Tab based on Adam. Do we know if there is an effort to port this ROM to G-Tab? Any info would be appreciated as this looks to be THE ROM, with the possibility of fixing camera and hardware acceleration.
A kernel is being worked on ; on the slatedroid forum. The hardware is different so a kernel has to be made for it to work
[email protected]: Posted Today, 09:31 AM
Unfortunately the Vega is not a hardware match for our beloved g-tab, they are very similar however they are not the same hardware exactly, little things like the wireless controller and the camera are different. They also have a different mainboard in their system. I'm pretty sure that the rom that works on theirs is not going to work on ours until we have a working kernel to work from. They have worked very hard on rewriting the drivers to get their tablet to work as well as it is in 3.2 and they don't seem to be slowing down now that it is working. I know that the group that is working on the kernel is working very hard to get it running as quickly as we can, I don't think that most of us have much experience in kernel coding and so it is taking some time to even get it to boot. However I can tell you that we are working diligently to get through the problems and get a kernel out to the community so that we can join the ranks of the Vega in making Google cry by hacking our way to victory. On a side note I want to say how impressed I am by the level of assistance that everyone in this community has for the new members and old members alike. I don't know of another rom that has this level of support from it's users out there. Thanks to all of you that are helping people overcome their issues and enjoy this fantastic rom.
Click to expand...
Click to collapse
.
[email protected] Posted 14 August 2011 - 09:01 PM
Hello all, Ch3vr0n5 here
The GTab Kernel Dev Team would like to chronicle our kernel development process for everyone to enjoy. The Gtablet 2.6.36 kernel project is based on the work done by Eduardo/RaYmAn on the Adam kernel. The biggest thanks goes out to them and anyone else who works on that project because it has made our work possible.
The Dev team is currently: Myself, Icewyng, Mayday_Jay, WayneMasta, Treznorx
[8/25/2011]
We know that we are hanging on init.rc and have a few ideas one how to proceed. Mayday_Jay (Give him and Icewyng a big thank you because they have made this project viable) is working on getting all the developers a proper update.zip that will help those with out a usb to serial converter get some useful debug information.
Don't fret when it takes a couple days for us to update. If you want bleeding edge news, join us on the kernel dev irc channel which is found further on in the thread. We are still working! =)
[8/23/2011]
Linux (BT5) will boot without Touchscreen working. Work is progressing slowly to get this working with Android. Mayday_Jay, with the use of USB -> serial converter has been able to get some useful dmesg output as well as some other debug information that is giving us new ideas on how to proceed.
[8/19/2011]
Starting to modify the adam files to mach the correct values for our device. Our current config gets us passed the birds and to the second boot image and the usb device registers. Trying to get it connected to adb to get some dmesg output.
[8/14/2011]
The resulting kernel did not boot and this is more than likely due to the fact that there are quite a few new config options that need to be set. I have run a diff to find differences between Pershoot's and Rayman's kernel and will be trying a new config either tonight or tomorrow hopefully. Gotta sift through new and deprecated options as well as any they both have but are set differently (and why)
Part 2
The kernel compiled with the additions from rayman's config in pershoots got it past the birds to the "Android 3.0" screen. Tomorrow I will be able to hookup adb and see where it is crashing from there.
[8/15/2011]
Still running through different configurations. Need to ask pershoot what modifications he made to make the .32 kernel boot on the 1.2 bootloader. IE Which files use the NEWBL config option and what the changes are.
[8/16/2011]
I received the source for the Vega kernel from rebel1. I may not update for a few days as I try out different configs and such but I will still be here.
[8/17/2011]
Decided to go with the Adam kernel because of hardware compatibility. Put up the github repo.
GitHub.com Repo
git://github.com/ch3vr0n5/android-tegra-2.6.36-gtablet.git
-----------------------
All thoughts, idea, comments and criticisms are welcome (Please be kind). Just remember, most of us are not programmers or software engineers by trade. I got my degree in network security so I generally play with routers, firewalls and the like and do this as a hobby. If you find anything wrong with what I or any of the Dev team have written please tell me... just don't point and laugh. LOL
Cheers
Click to expand...
Click to collapse
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? ??
Hi,
I'm not sure if this is is an appropriate request for this forum.
I'm working on a hardware modification for my old Droid Mini, and I found after a couple months of HW tinkering that my solution requires kernel support which does not exist on the kernel running on the device.
The matter in question is upgrading / backporting the SCSI autosuspend infrastructure to an MSM9860DT kernel.
I've consulted with a developer who thinks the modification may take a few days of work (they don't have the time at the moment) , so I don't think it is a highly complex, from-scratch project for someone who knows kernel development (then again, I may be very wrong - this is not my field whatsoever)
Is there anyone here who may have some time / interest in poking at this, or knows someone who might?
Cheers,
Rafael
I've recently bought a surface go for school (64gb emmc, 4gb ram model) and I love the pen and the build quality however i found windows to be way to slow on a device like this and decided to try android. android-x86_64-8.1-r2 installed fine and it runs great on this hardware except for a few issues such as camera, auto rotate and the like. I've run into a pre-made kernel that fixes these issues and will link it below. I was wondering if someone could help me with implementing this kernel into android x86 to get the full set of features working. Thanks in advance!
Kernel:
(On github) /jakeday/linux-surface/releases
Could you tell me how you implemented that pre-made kernel into Android x86? I'm trying to do the same thing with Bliss OS 11.10 (Kernel 4.19), but I really don't know how. I could have missed something on the GitHub page, but I don't know how to implement a kernel into Android. To be honest, I never implemented a Linux kernel into an OS.
I hope you read this even though it's already been a few months.
Thank you
Hello to everyone.
I would like to understand how to emulate a recent version of Android on my jetson nano with qemu / kvm. I already have some experience with linux,with the jetson nano and with the arm64 platform,but a very little one with Android. But I have already asked some crucial informations about the most important requisites that Android should have to run with qemu-kvm. Basically these :
An Android image with Mesa DRM/KMS support.
Android kernel with the appropriate Virtio-gpu modules enabled.
Modified Jetson nano kernel to add support for KVM
compiled Virgilrender and qemu with virgilrender support
I have already configured point 3 and 4. Point 1 and 2 are missing 'cause I have a little Android knowledge. Someone said to me "It needs to be one targeted for Qemu with virtio-gpu support enabled. There are images around with it configured but don’t have ones that I can share". Ok. for me its better to understand how to configure Android from the beginning like it should be,but I'm pragmatic,so I don't say no if someone wants to give me a recent Android image already configured . In any case,since I don't know where to start,I would like to get some detailed documentation from you,because I want to learn the workflow. Thanks in advance.
no one wants to help here ?