[Bug 571663] [NEW] ti-omap flavor of ubuntu-lucid kernel does not include cm-t35 board

Lee Jones lee.jones at canonical.com
Wed Jul 28 08:23:50 UTC 2010


On 28/07/10 08:46, Mike Rapoport wrote:
> On Wed, Jul 28, 2010 at 10:39 AM, Amit Kucheria <amit.kucheria at canonical.com
>> wrote:
> 
>> On 10 Jul 28, Eric Miao wrote:
>>> On Wed, Jul 28, 2010 at 2:57 PM, Lee Jones <lee.jones at canonical.com>
>> wrote:
>>>> Hi Mike,
>>>>
>>>> As I've said before and mentioned on the bug report, the team
>> (including myself) do not have the available time to search for a suitable
>> fix, as this board is not supported by us. I have spoken with Amit, who I
>> believe you've been in contact with, who echoed my thoughts. I was hoping
>> for some spare time to deal with the problem, but 'spare time' isn't a
>> commonly muttered phrase within the Kernel Team, without 'I wish I had'
>> prepended. Unfortunately, the Beagleboard has to take precedence over the
>> CM-T35. If it means that much to you, either purchase a Beagleboard and
>> complete the work yourself, or I can try (I'll make no promises, as my
>> private life is just as busy) to take a look in my spare time.
>>>>
>>>> Does anyone have a CM-T35 that I can borrow for this?
>>>
>>> Hi Mike,
>>>
>>> My understanding is that you can provide patches for beagleboard to
>>> boot with CONFIG_OMAP_MUX. Things will be much easier if this
>>> patch is able to hit upstream.
>>>
>>> I think it will be good at this time if you could help build a kernel
>> with
>>> your patches and for others to verify if it's breaking the beagleboard.
>>> Once the patches are merged/Acked into -stable or .35, they are
>>> supposed to be merged later into -lucid and -maverick.
>>>
>>
>> Mike,
>>
>> Please get those patches acked upstream. I feel there is still some work
>> needed to get them in shape.
>>
>> Three of four patches are in the Linus tree.
> I can't push the hack for the BeagleBoard because it's a hack and not a fix.
> Inability of BeagleBoard to boot with CONFIG_OMAP_MUX=y is a bug that IMO
> deserves a proper fix on it's own.

Quite right.




More information about the kernel-team mailing list