All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: "Woodruff, Richard" <r-woodruff2@ti.com>,
	linux-omap-open-source@linux.omap.com
Subject: Re: GPMC timings for smc91x on 24xx (WAS: Pending July patches)
Date: Sun, 13 Aug 2006 16:42:01 +0200	[thread overview]
Message-ID: <44DF3A39.7010302@gmail.com> (raw)
In-Reply-To: <EA12F909C0431D458B9D18A176BEE4A506F16C69@dlee02.ent.ti.com>

Woodruff, Richard wrote:
...
> No body waits.
...
> OMAP3 isn't so far off. 
...
>>>Thanks for the good work.
>>
>>Whatever. Rather thank Komal for all the good work on merging TI code.
> 
> Generally we try and help where we can in this forum.  I do help Komal
> and you and others where I can.  Boards, data clarification, some
> code...

Maybe TI can consider to create something like a OSK for 
OMAP2 and/or OMAP3? It's my feeling that there are many 
people who are able and willing to work on OMAP code, and 
OSK was a big success regarding this.

But I think for this easy access to HW and documentation is 
necessary. I think not everybody who is able and willing to 
help improving OMAP code has a purchasing department, 
lawyers, project managers and all this stuff which sometimes 
seems to be necessary to get the HW and information to help.

Opinions?

Regards

Dirk

  parent reply	other threads:[~2006-08-13 14:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03 15:57 GPMC timings for smc91x on 24xx (WAS: Pending July patches) Woodruff, Richard
2006-08-03 16:22 ` Dirk Behme
2006-08-03 18:55 ` tony
2006-08-13 14:42 ` Dirk Behme [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-13 15:49 Woodruff, Richard
2006-08-03 22:37 Woodruff, Richard
2006-08-03 16:23 Woodruff, Richard
2006-08-03 14:20 Woodruff, Richard
2006-08-03 15:00 ` Tony Lindgren
2006-08-03 16:00 ` Juha Yrjölä
2006-08-03 11:17 Pending July patches Tony Lindgren
2006-08-03 12:08 ` Komal Shah
2006-08-03 13:03   ` GPMC timings for smc91x on 24xx (WAS: Pending July patches) Tony Lindgren

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=44DF3A39.7010302@gmail.com \
    --to=dirk.behme@googlemail.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=r-woodruff2@ti.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.