On 12/11/2012 12:04 AM, Greg KH wrote:
On Mon, Dec 10, 2012 at 11:53:27PM +0100, Timur wrote:
N7 is not using a vanilla kernel.
Yes, I know that quite well :)
It is one thing to apply
modifications to the given code base. It would be far more difficult
(I think) to replace the kernel as a whole. Maybe I should back port
just as little code as possible? Or maybe I should try to back port
some full building blocks? Where to make the cut? I also wonder how
to make the system take advantage of ehci_suspend() and
ehci_resume(), both marked as "__maybe_unused". Who is calling these
methods?
Look at the newer kernels for what is going on there.
As for which is easier, that's up to you, there has been a lot of work
to integrate the out-of-tree tegra and android code and get it merged to
the main kernel since 3.1 was released over a year ago, so it depends on
what you feel comfortable with doing.
Wow, I was not aware of this. Can you please point me to a N7-compatible
configuration for a more recent kernel?
However, unless you are running the latest kernel.org release, there's
usually not much we can help you out with here, as we don't know, or
remember, what is going on in that very old release + odd-random-android
patches.
good luck,
Thank you.
Timur
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
