RE: [RFC 0/5] OMAP4: mux: Add the OMAP4430 ES1 support

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> -----Original Message-----
> From: Cousson, Benoit
> Sent: Monday, October 18, 2010 3:57 PM

> >>>> From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap-
> >>>> owner@xxxxxxxxxxxxxxx] On Behalf Of Benoit Cousson
> >>>>
> >>> Ping? Is there a possibility for a v2 non-rfc ES2 support?
> >>
> >> And what about a RFC v2? With ES2 support of course :-)
> >>
> >> The changes I have done are breaking RX51 support due to the usage of
> >> low-level API from the mux code.
> >>
> >> For the moment I just disabled that code from the RX51, so there is no
> >> way I send that except in a RFC form :-(
> > It'd be good to evolve this further.. looks like there is a bunch of
> > Drivers pending posting due to "lack of mux framework"..
> 
> I guess that the current code should be good enough for that, isn't it?
> The main API will not change. Only the low API will become forbidden.

Unfortunately, not in l-o or kernel.org means not upstreamed solution :(
That is not a codebase for any driver developer to build on unfortunately :(.

Regards,
Nishanth Menon

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux