From: Peter Korsgaard <peter.korsgaard@barco.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: [RFC] SystemACE driver - abstract register ops
Date: Wed, 02 May 2007 15:23:16 +0200 [thread overview]
Message-ID: <87d51j5ph7.fsf@sleipner.barco.com> (raw)
In-Reply-To: <20070427173010.620DE4B8073@mail25-fra.bigfish.com> (Wolfgang Reissnegger's message of "Fri, 27 Apr 2007 10:30:08 -0700")
>>>>> "WR" == Wolfgang Reissnegger <wolfgang.reissnegger@xilinx.com> writes:
Hi,
WR> The end goal is to have a kernel tree that contains ALL Xilinx
WR> drivers and the multitude of drivers that are being
WR> created/updated and contributed here. Having such a kernel
WR> available will simplify the process of bringing up a new
WR> system. The hope is that contributors will adopt the idea of
WR> having a "Xilinx" kernel and will start using that tree as a "base
WR> reference".
But there already is such a tree - It's called 'mainline'. I can see
some advantage in having a Xilinx tree as a staging area, but it
really HAS to be a temporary thing and stuff needs to be pushed to
mainline.
WR> I will post news here as they unfold. In the meantime it would be
WR> very interesting to hear ideas and suggestions from you. Concerns
WR> that people have. Pitfalls to look out for etc.
Hereby my 2 cents.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2007-05-02 13:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 6:36 [RFC] SystemACE driver - abstract register ops John Williams
2007-04-27 6:48 ` Grant Likely
2007-04-27 7:31 ` Grant Likely
2007-04-27 12:11 ` Stefan Roese
2007-04-27 17:30 ` Wolfgang Reissnegger
2007-05-02 13:23 ` Peter Korsgaard [this message]
2007-05-02 16:50 ` Wolfgang Reissnegger
2007-04-27 18:38 ` Andrei Konovalov
2007-04-27 18:42 ` Grant Likely
2007-05-01 3:42 ` John Williams
2007-05-01 3:53 ` Grant Likely
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=87d51j5ph7.fsf@sleipner.barco.com \
--to=peter.korsgaard@barco.com \
--cc=linuxppc-embedded@ozlabs.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 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.