From: Tom Rini <trini@kernel.crashing.org>
To: Pantelis Antoniou <panto@intracom.gr>
Cc: Dan Malek <dan@embeddededge.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: 8xx drivers for 2.6
Date: Mon, 15 Dec 2003 09:18:15 -0700 [thread overview]
Message-ID: <20031215161815.GC23731@stop.crashing.org> (raw)
In-Reply-To: <3FDDA552.7030007@intracom.gr>
On Mon, Dec 15, 2003 at 02:13:06PM +0200, Pantelis Antoniou wrote:
> Tom Rini wrote:
> >On Thu, Dec 11, 2003 at 02:44:50PM -0500, Dan Malek wrote:
> >>Tom Rini wrote:
> >>
> >>>Ok. I've gone and ported the 8xx serial driver, and other misc 8xx
> >>>things up to what 2.6 wants them to be, as well as a few of the
> >>>simpler changes to head_8xx.S.
> >>>
> >>>
> >>Thanks. So, does the kernel at least compile now? :-)
> >>
> >
> >Compiles, links, boots and happily dies inside of head_8xx.S :)
> >
> >>>...and in 2.6 having request_8xxirq becomes much uglier because of
> >>>the irqreturn_t stuff
> >>>
> >>>
> >>I'm finally going to update this. I've got a pretty good implemenation
> >>of the cascaded controller stuff for the 8560, once I get this
> >>debugged I'll port it here.
> >
> >Sounds like a plan.
> >
> >>>Dan, if you have _anything_ done for head_8xx.S can you please post
> >>>it?
> >>>
> >>Yeah, maybe I can do some debug now, too.
> >>
> >
> >Hopefully :)
>
> That sounds nice.
>
> Any chance to push the changes to the linuxppc-2.5 tree for us poor saps?
> It doesn't have to work or anything, just give us something to work...
Sure, done.
--
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-12-15 16:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 19:18 8xx drivers for 2.6 Tom Rini
2003-12-11 19:44 ` Dan Malek
2003-12-11 21:25 ` Tom Rini
2003-12-15 12:13 ` Pantelis Antoniou
2003-12-15 16:18 ` Tom Rini [this message]
2003-12-21 12:31 ` Geert Uytterhoeven
2003-12-21 21:39 ` Paul Mackerras
2003-12-22 9:00 ` Dan Malek
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=20031215161815.GC23731@stop.crashing.org \
--to=trini@kernel.crashing.org \
--cc=dan@embeddededge.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=panto@intracom.gr \
/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;
as well as URLs for NNTP newsgroup(s).