• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help In theory: Eclair on Galaxy

U

ultrakomm

Newbie
What is stopping us from compiling a proper Eclair kernel for Galaxy? Didn't Samsung just recently release the sources code for Galaxy, including drivers etc?

Couldn't one take the source from some Eclair-enabled phone and compile it with the appropriate Galaxy drivers?

What more would be needed to make it work? Do the drivers Samsung released the source for only work on the current kernel (2.6.27), and not on the Eclair kernel?
 
ultrakomm said:
What is stopping us from compiling a proper Eclair kernel for Galaxy? Didn't Samsung just recently release the sources code for Galaxy, including drivers etc?
Click to expand...
I seem to recall that not all of the drivers were included. (Which is fine, btw, from a legal standpoint: Android may be GPL'ed, but the hardware and its drivers aren't and don't need to be.)

Maybe the question is, does Android 2.0 require multi-touch hardware, or can it be made to run on a simple touch screen?
 
KlaymenDK said:
Maybe the question is, does Android 2.0 require multi-touch hardware, or can it be made to run on a simple touch screen?
Click to expand...

I doubt it requires multitouch. Although galaxy does have multitouch, the driver is broken and it doesn't send events for the few first fingers. There was an extensive blog post about this somewhere.
 
ultrakomm said:
What is stopping us from compiling a proper Eclair kernel for Galaxy? Didn't Samsung just recently release the sources code for Galaxy, including drivers etc?

Couldn't one take the source from some Eclair-enabled phone and compile it with the appropriate Galaxy drivers?

What more would be needed to make it work? Do the drivers Samsung released the source for only work on the current kernel (2.6.27), and not on the Eclair kernel?
Click to expand...
Eclair kernel is 2.6.29 I think
 
KlaymenDK said:
I seem to recall that not all of the drivers were included. (Which is fine, btw, from a legal standpoint: Android may be GPL'ed, but the hardware and its drivers aren't and don't need to be.)

Maybe the question is, does Android 2.0 require multi-touch hardware, or can it be made to run on a simple touch screen?
Click to expand...

Actually the kernel does contain non-GPL drivers. Funny thing is, they included them in the source release. Already reported that on gpl-violations.org

I think the problem is there are various userspace components for which source is not available (BSD Licensed). These components are linked against 1.5 stuff and probably need both modifications for 1.6/2.0 and need to be relinked.
 
Russ, tnx for that. I hope that would trigger some manager in Samsung to employ more people in r&d.
 
Andronix said:
Russ, tnx for that. I hope that would trigger some manager in Samsung to employ more people in r&d.
Click to expand...

I don't think much can be done as far as their Linux development teams in the long or short term. Looking at the contents of my Samsung TV and the accompanying source release shows more of the same. A whole lot of NIH and working against the grain in addition to GPL violations (haven't gotten around to fully investigating that, so far I've noticed that the shipped busybox and the source release busybox are not the same version). I'm surprised that the phone doesn't somehow utilize Samsung's proprietary RFS filesystem.

I'd be nice if they would hire a GPL compliance officer.
 
You must log in or register to reply here.
Back
Top Bottom