From: Pantelis Antoniou <panto@intracom.gr>
To: Dan Malek <dan@embeddededge.com>
Cc: Paul Mackerras <paulus@samba.org>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: the door is closing for 2.4
Date: Fri, 05 Dec 2003 09:24:49 +0200 [thread overview]
Message-ID: <3FD032C1.9060504@intracom.gr> (raw)
In-Reply-To: <3FCF540C.3010302@embeddededge.com>
Dan Malek wrote:
> Pantelis Antoniou wrote:
>
>> Once upon a time I had it at least compile, but for my board only.
>> But then you mentioned you were working on it and I dropped it.
>
>
> I had been working on it, primarily to get the processor specific
> changes done.
>
>> Could you please elaborate on the tasks that need to be done?
>> I know that the head_8xx.S file definetely needs alot of work,
>> and you mentioned the drivers.
>
>
> The serial driver doesn't compile since the serial subsystem was
> reworked. The old data structures used to represent port
> information (in particular serial_state) no longer works.
> Yes, head_8xx.S needs lots of work, but to me that is the easy part :-)
Well if you can get head_8xx.S in some decent shape I can get it to boot
since in a board of mine I don't use the built-in uart but an external
MAX3100.
Do the serial drivers based on the generic_serial interface still work
in 2.6?
>
>
>> What is the minimum stuff needed to make it work at least for my
>> boards?
>
>
> Make it compile again, I'll take it from there.
OK, I'll try (maybe with taking out the 8xx uart out completely).
>
>> I'd be happy to help at least as long as my busy schedule permits.
>
>
> Me, too. Just don't be annoyed if it takes me a while to respond,
> especially if testing changes is involved.
>
> Thanks.
>
>
> -- Dan
>
>
>
>
And finally do you think it makes sence to try to consolidate the 8xx
and 82xx drivers?
If we're going to need some major restructuring and/or rewrite of the
drivers that
makes sense IMHO.
Regards
Pantelis
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-12-05 7:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 0:34 the door is closing for 2.4 Paul Mackerras
2003-12-04 9:16 ` Pantelis Antoniou
2003-12-04 13:55 ` Dan Malek
2003-12-04 15:06 ` Pantelis Antoniou
2003-12-04 15:34 ` Dan Malek
2003-12-05 7:24 ` Pantelis Antoniou [this message]
2003-12-05 18:54 ` Dan Malek
2003-12-04 9:47 ` Stefan Roese
2003-12-05 0:08 ` Kumar Gala
2004-01-12 5:30 ` Paul Mackerras
2003-12-10 15:38 ` Hubert Figuiere
2003-12-10 16:55 ` Tom Rini
2003-12-10 16:57 ` Hubert Figuiere
2003-12-10 19:19 ` Tom Rini
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=3FD032C1.9060504@intracom.gr \
--to=panto@intracom.gr \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=paulus@samba.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.