Announcement
Collapse
No announcement yet.
Announcement
Collapse
No announcement yet.
CM11 for A/S8 (in-progress)
Collapse
X
-
I don't know anything about programming, and I really wish I did, in fact, I want to study it. Anyways, I just want to say that you guys are awesome!!!!! I find it fantastic that you guys take time to help out strangers whose as/8 has been a big disappointment, I thank you all for your hard work!
Comment
-
Made progress on the Cubieboard2 kernel. It actually goes past the Polaroid logo and is met with a grey screen. It's most likely a missing LCD module (a CB2 is a board without a touchscreen) I have the CB2's source code and it includes a "Cubieboard2-LCD" option upon lunching. Will look into this.
Comment
-
Originally posted by AManofFewWords View PostMade progress on the Cubieboard2 kernel. It actually goes past the Polaroid logo and is met with a grey screen. It's most likely a missing LCD module (a CB2 is a board without a touchscreen) I have the CB2's source code and it includes a "Cubieboard2-LCD" option upon lunching. Will look into this.
Comment
-
Originally posted by AManofFewWords View PostMade progress on the Cubieboard2 kernel. It actually goes past the Polaroid logo and is met with a grey screen. It's most likely a missing LCD module (a CB2 is a board without a touchscreen) I have the CB2's source code and it includes a "Cubieboard2-LCD" option upon lunching. Will look into this.
you need to compile the hardware drivers with the kernel source... you have two options for the maili drivers.. you either use the proprietary drivers which are currently closed source (as far as i know) or you can use the open source mali drivers (still a work in progress) for an almost as-good alternative. you can get the open source alternative from malideveloper.arm.com (or something like that)..
btw, great work..
Comment
-
Originally posted by AManofFewWords View PostThe problem is that the ramdisk contains kernel modules as well, actually, the basic modules to use the tablet (lcd.ko, hdmi.ko, disp.ko, touch.ko) The other modules the tablet needs can already be preinstalled inside the kernel during compilation.
I wouldn't advise compiling all the drivers inside the kernel.. It will make your kernel bloated (bigger) and slower to boot.. Depending on which kernel you are building - (if kernel 3.3)there is a chance of using existing modules from the device. You will see the modules inside the vendor folder on the system partition.
The modules that are contained inside the ramdisk is used to start the initial support for device operations. During the init.${hardware}.rc init process (which is imported by init.rc) the other modules are activated when called upon.
The time saved by the kernel not having to outsource for modules have been overcome by speeds of current architectures. You may be able to completely strip the kernel of all things not needed and run only basic devices to improve speeds in that manner. However, it is not a common practice at this time. Things have changed since the old days.
Also, you may find some device drivers that will only compile as modules.
Comment
What's Going On
Collapse
There are currently 1918 users online. 1 members and 1917 guests.
Most users ever online was 63,956 at 18:56 on 20 March 2025.
Comment