linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Pantelis Antoniou <panto@intracom.gr>
To: Dan Malek <dan@embeddededge.com>
Cc: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>,
	Paul Mackerras <paulus@samba.org>,
	Tom Rini <trini@kernel.crashing.org>
Subject: Re: [2.5] Hang on 8xx in head_8xx.S
Date: Fri, 14 Feb 2003 16:07:12 +0200	[thread overview]
Message-ID: <3E4CF810.8040803@intracom.gr> (raw)
In-Reply-To: <3E4CF139.2040909@embeddededge.com>


Dan Malek wrote:

> Pantelis Antoniou wrote:
>
>> Cool. How can I help?
>
>
> Once I get it basically booting there are lots of little things in
> drivers that need updating.
>
>> Could you take the time to  highlight the changes needed?
>
>
> I'm not sure what all of them are just yet :-)
>
>> How about a discussion about some improvements?
>
>
> discuss away........
>
> Thanks.
>
>
>     -- Dan
>
>
>
>
Ok then ;)

1. I think it is time to look into the
artificial (IMO) division between 8xx_io/8260_io.

The CPM is basically the same, but there are two kind
of drivers for every peripheral that is common.

i.e. arch/ppc/8xx_io/enet.c arch/ppc/8260_io/enet.c

I believe we should have one common driver for both.

2. The profusion of platform specific #defines in the
drivers. Typically something like the configuration of
the port I/O for the ethernet/uart whatever.

How about having a platform specific source file
that will export functions for the platform specific
part of the configuration?

i.e. instead of

#if defined(CONFIG_XXX)
    .. blah ..
#elif defined(CONFIG_YYY)
    .. blah blah ..
....

something like this

    m8xx_platform_ethernet_port_config(int scc);

3. Ability to have the drivers built as modules.
I believe I have made my case in a previous mail
so I'll spare you this time.

How about taking a look at the patches I have sent
you earlier about the dpalloc/hostalloc problem?

Thanks for taking the time to  respond, and
when you get it booting I'm willing to work
at any of these areas.

Regards

Pantelis


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-02-14 14:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13 13:27 [2.5] Hang on 8xx in head_8xx.S Pantelis Antoniou
2003-02-13 16:50 ` Dan Malek
2003-02-14  7:33   ` Pantelis Antoniou
2003-02-14 13:38     ` Dan Malek
2003-02-14 14:07       ` Pantelis Antoniou [this message]
2003-02-14 20:31         ` Dan Malek
2003-02-14 21:30           ` Pantelis Antoniou
2003-02-16 17:12             ` Dan Malek
2003-02-16 19:38               ` Allen Curtis

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=3E4CF810.8040803@intracom.gr \
    --to=panto@intracom.gr \
    --cc=dan@embeddededge.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=paulus@samba.org \
    --cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).