Guest thisweb Posted September 18, 2010 Report Posted September 18, 2010 https://sites.google.com/site/thisweb123/t-...opment---modaco A technical flow diagram of how the current modaco development fits together. May be useful for newbies! I will try and keep this up to date with a plan to add some flowlinks and faqs as development progresess. Its tricky to find things in the forum at the moment, especially for fidlly tasks like enabling jit etc. Especially for newbies.
Guest AntonioPT Posted September 18, 2010 Report Posted September 18, 2010 https://sites.google.com/site/thisweb123/t-...opment---modaco A technical flow diagram of how the current modaco development fits together. May be useful for newbies! I will try and keep this up to date with a plan to add some flowlinks and faqs as development progresess. Its tricky to find things in the forum at the moment, especially for fidlly tasks like enabling jit etc. Especially for newbies. Nice! Good work :lol:
Guest DanWilson Posted September 18, 2010 Report Posted September 18, 2010 Good job, but we never had, nor will have, Donut. And you refer to the 1.5 ROM as being Donut. Otherwise, it's excellent! Although it's saddening to see so many things we didn't have till last week, and some things we may never get (But probably will!) :lol:
Guest JimJam707 Posted September 18, 2010 Report Posted September 18, 2010 Good job, but we never had, nor will have, Donut. And you refer to the 1.5 ROM as being Donut. Otherwise, it's excellent! Although it's saddening to see so many things we didn't have till last week, and some things we may never get (But probably will!) :lol: Whats 1.5 called?
Guest DanWilson Posted September 18, 2010 Report Posted September 18, 2010 Whats 1.5 called? Cupcake.
Guest JimJam707 Posted September 18, 2010 Report Posted September 18, 2010 Cupcake. I knew that. *cough* NO *cough*
Guest thisweb Posted September 18, 2010 Report Posted September 18, 2010 Good job, but we never had, nor will have, Donut. And you refer to the 1.5 ROM as being Donut. Otherwise, it's excellent! Although it's saddening to see so many things we didn't have till last week, and some things we may never get (But probably will!) :lol: Doh!!!! Mmm... Donuts! Thanks I've corrected that.
Guest AntonioPT Posted September 18, 2010 Report Posted September 18, 2010 Are you sure the drivers are closed source? I mean, aren't they included in the kernel source?
Guest AdamBaker Posted September 18, 2010 Report Posted September 18, 2010 Are you sure the drivers are closed source? I mean, aren't they included in the kernel source? There are 2 sorts of driver, kernel drivers (these can be either compiled in or provided as .ko files) and the drivers that provide a user space interface to android (these are some but not all of the .so files). Most of the kernel drivers are included as part of the kernel source, the only exception is the WiFi which is supplied as a closed source .ko file. We will need new versions of this t work with new kernels, either by finding another phone with compatible hardware or by porting the version in the OpenMoko repository. The Userspace drivers are the bigger potential problem, while the kernel drivers remain the same (which we can ensure) and the android interfaces remain the same (which is harder to control) we can continue using the existing closed source ones. At the moment the drivers for interfaces for the sensors (compass, accelerometers etc) have remained compatible, Tom G has tracked down source code for compatible audio drivers and I am working to pull together changes that Cyanogen has made to return the interfaces the camera driver needs to those in eclair. Going forward I see the camera as the biggest problem because there is little public documentation of how it is controlled.
Guest Simon O Posted September 18, 2010 Report Posted September 18, 2010 There are 2 sorts of driver, kernel drivers (these can be either compiled in or provided as .ko files) and the drivers that provide a user space interface to android (these are some but not all of the .so files). Most of the kernel drivers are included as part of the kernel source, the only exception is the WiFi which is supplied as a closed source .ko file. We will need new versions of this t work with new kernels, either by finding another phone with compatible hardware or by porting the version in the OpenMoko repository. The Userspace drivers are the bigger potential problem, while the kernel drivers remain the same (which we can ensure) and the android interfaces remain the same (which is harder to control) we can continue using the existing closed source ones. At the moment the drivers for interfaces for the sensors (compass, accelerometers etc) have remained compatible, Tom G has tracked down source code for compatible audio drivers and I am working to pull together changes that Cyanogen has made to return the interfaces the camera driver needs to those in eclair. Going forward I see the camera as the biggest problem because there is little public documentation of how it is controlled. I've got the .32 compatible wifi blob from the U8150 ROM. ar6000.ko but it doesn't work with .29 kernels. ar6000_2.6.32wifi.zip There are probably other bits that will be useful for us. The U8150 has the same wifi and same processor as the Pulse (MSM7201A). Obviously the .32 kernel source from Huawei for that phone would be even better... but who wants to place a bet on how long this will take? lol
Guest DanWilson Posted September 18, 2010 Report Posted September 18, 2010 I've got the .32 compatible wifi blob from the U8150 ROM. ar6000.ko but it doesn't work with .29 kernels. ar6000_2.6.32wifi.zip There are probably other bits that will be useful for us. The U8150 has the same wifi and same processor as the Pulse (MSM7201A). Obviously the .32 kernel source from Huawei for that phone would be even better... but who wants to place a bet on how long this will take? lol 9,000,000,000,000 years. Can't we do a rough job like we did with the Pulse? But just the kernel instead of all the system.
Guest DanWilson Posted September 18, 2010 Report Posted September 18, 2010 I've got the .32 compatible wifi blob from the U8150 ROM. ar6000.ko but it doesn't work with .29 kernels. ar6000_2.6.32wifi.zip There are probably other bits that will be useful for us. The U8150 has the same wifi and same processor as the Pulse (MSM7201A). Obviously the .32 kernel source from Huawei for that phone would be even better... but who wants to place a bet on how long this will take? lol 9,000,000,000,000 years. Can't we do a rough job like we did with the Pulse? But just the kernel instead of all the system.
Guest AdamBaker Posted September 18, 2010 Report Posted September 18, 2010 I've got the .32 compatible wifi blob from the U8150 ROM. ar6000.ko but it doesn't work with .29 kernels. ar6000_2.6.32wifi.zip There are probably other bits that will be useful for us. The U8150 has the same wifi and same processor as the Pulse (MSM7201A). Obviously the .32 kernel source from Huawei for that phone would be even better... but who wants to place a bet on how long this will take? lol I wouldn't expect the blob from a .32 kernel to work with .29 but if we port the Huawei bits from the .29 kernel to .32 then it will be the last step in the chain to getting a working .32. Tom has made a start on this approach with the kernel he can use to boot the recovery image. I'd suggest next step is the jogball driver as that would make the recovery image usable and shouldn't be too bad to convert, especially as it is © Google / Qualcomm, not Huawei so may even be in the Android .32, probably with different values for the GPIO pins at the start of kernel/arch/arm/mach-msm/jogball_device.c
Guest Tom G Posted September 19, 2010 Report Posted September 19, 2010 I've got the .32 compatible wifi blob from the U8150 ROM. ar6000.ko but it doesn't work with .29 kernels. ar6000_2.6.32wifi.zip There are probably other bits that will be useful for us. The U8150 has the same wifi and same processor as the Pulse (MSM7201A). Obviously the .32 kernel source from Huawei for that phone would be even better... but who wants to place a bet on how long this will take? lol That could be useful. I haven't had much time to play with the kernel (FLB-Mod 2 is finding so many problems in froyo), but if I can get the module to load and get an ssh server running that could provide a way for others to play with a .32 kernel without soldering an rs232 port onto their phone. I think there are a lot of things to fix before that will work, but maybe in a few weeks it will work (it barely boots now, and although I can get the kernel output redirected to ttyMSM2, I can't get a cmdline).
Guest Simon O Posted September 19, 2010 Report Posted September 19, 2010 That could be useful. I haven't had much time to play with the kernel (FLB-Mod 2 is finding so many problems in froyo), but if I can get the module to load and get an ssh server running that could provide a way for others to play with a .32 kernel without soldering an rs232 port onto their phone. I think there are a lot of things to fix before that will work, but maybe in a few weeks it will work (it barely boots now, and although I can get the kernel output redirected to ttyMSM2, I can't get a cmdline). I'm glad FLBmod 2 is allowing people to find bugs in Froyo. Like the wifi mac address bug, I wouldn't have noticed it if people didn't report issues with wifi.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now