From: Mike Rapoport <mike@compulab.co.il>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: Cliff Brake <cliff.brake@gmail.com>, linux-omap@vger.kernel.org
Subject: Re: several OMAP newbie questions
Date: Tue, 15 Sep 2009 09:16:38 +0300 [thread overview]
Message-ID: <4AAF3146.4040308@compulab.co.il> (raw)
In-Reply-To: <4AAE5F5C.1000902@deeprootsystems.com>
Kevin Hilman wrote:
> Mike Rapoport wrote:
>> Hi Kevin,
>>
>> Kevin Hilman wrote:
>>> There is lots of agreement around the various shortcomings of the
>>> current mux framework for OMAP. All that's missing is someone to step
>>> up and do the work. :/
>>>
>>> I started a new wiki topic at elinux.org for linux-omap wishlist items:
>>>
>>> http://elinux.org/OMAP_wishlist
>>>
>>> here I created a pin-mux section where we could start to keep track of
>>> the important features needed in a new mux framework. Adding pointers
>>> summaries to some other platforms might be useful here as well.
>>
>> If you'd like to I can add a brief description of what PXA does.
>>
>
> Sure, could be useful.
Done. :)
> Thanks,
>
> Kevin
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2009-09-15 6:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 10:34 several OMAP newbie questions Mike Rapoport
2009-09-04 22:08 ` Cliff Brake
2009-09-09 14:51 ` Mike Rapoport
2009-09-10 16:09 ` Kevin Hilman
2009-09-13 13:07 ` Mike Rapoport
2009-09-14 15:21 ` Kevin Hilman
2009-09-15 6:16 ` Mike Rapoport [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AAF3146.4040308@compulab.co.il \
--to=mike@compulab.co.il \
--cc=cliff.brake@gmail.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox