From: "Luke Yang" <luke.adi@gmail.com>
To: "Andrew Morton" <akpm@osdl.org>
Cc: "Robin Getz" <rgetz@blackfin.uclinux.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2]Blackfin archtecture patche for 2.6.16
Date: Wed, 22 Mar 2006 15:42:14 +0800 [thread overview]
Message-ID: <489ecd0c0603212342w4124dddfy1bb50c02984c0e8f@mail.gmail.com> (raw)
In-Reply-To: <20060321223652.25bf07f7.akpm@osdl.org>
On 3/22/06, Andrew Morton <akpm@osdl.org> wrote:
> Robin Getz <rgetz@blackfin.uclinux.org> wrote:
> >
> > Luke Yang wrote:
> > >On 3/21/06, Andrew Morton <akpm@osdl.org> wrote:
> > > > - How widespread/popular is the blackfin? Are many devices using it?
> > > > How old/mature is it? Is it a new thing or is it near end-of-life?
> > > As a DSP, Blackfin has been there for years and is somewhat popular.
> > >But as a CPU which can run Linux, we are trying to make it popular.
> > >Anyway a 5$ chip runs Linux and can do audio/video codec is a good toy to
> > >play with.
> >
> > I would not describe it as a toy (sorry Luke),
> >
> > [ interesting info ]
> >
>
> Thanks.
>
> > If you think our patch sucks, fine - let us know where to fix it.
>
> It looks reasonable to me, from a ten-minute-scan.
>
> Well. All architecture ports suck. Yours sucks averagely ;)
>
> The todo list of which I'm aware is
>
> - use serial core in that driver
>
> - Fix up that ioctl so it a) doesn't sleep in spinlock and b) compiles
>
> - Use generic IRQ framework
>
> - Review all the volatiles, consolidate them in some helper-in-header-file.
>
> - Sort out maintainance issues, gather signed-off-bys. (Done, it appears)
>
> More things might come out once people start paying more attention, but if
> that's the extent of things, I'd be OK with a merge when you're ready.
Does this merge has to be within 1 week after the release, so we
have to wait for 2.6.17? Or this can be done on mm-tree?
>
--
Best regards,
Luke Yang
magic.yyang@gmail.com; luke.adi@gmail.com
next prev parent reply other threads:[~2006-03-22 7:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 6:12 Robin Getz
2006-03-22 6:36 ` Andrew Morton
2006-03-22 7:42 ` Luke Yang [this message]
2006-03-22 7:49 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2006-03-20 10:00 Luke Yang
2006-03-21 7:30 ` Luke Yang
2006-03-21 11:14 ` Andrew Morton
2006-03-21 23:45 ` Bernd Schmidt
2006-03-22 0:32 ` Andrew Morton
2006-03-22 3:45 ` Luke Yang
[not found] ` <20060321194848.4d041ab5.akpm@osdl.org>
2006-03-22 4:47 ` Luke Yang
2006-03-22 23:43 ` Ingo Oeser
2006-03-23 7:20 ` Luke Yang
2006-03-23 10:21 ` Philippe Gerum
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=489ecd0c0603212342w4124dddfy1bb50c02984c0e8f@mail.gmail.com \
--to=luke.adi@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rgetz@blackfin.uclinux.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
all inboxes | Powered by JetHome®