From: Matt Porter <porter@cox.net>
To: Brian Waite <waite@skycomputers.com>
Cc: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: RFC: gt64260 descriptor struct
Date: Thu, 27 Feb 2003 09:27:01 -0700 [thread overview]
Message-ID: <20030227092701.A15982@home.com> (raw)
In-Reply-To: <200302271031.27317.waite@skycomputers.com>; from waite@skycomputers.com on Thu, Feb 27, 2003 at 10:31:27AM -0500
On Thu, Feb 27, 2003 at 10:31:27AM -0500, Brian Waite wrote:
> What we need is a global structure for gt code that will describe the features
> of the gt and export that to drivers that need it. What I see right now for
> required elements are:
All peripherals that don't have intelligent discovery mechanisms could
make use of the OCP layer that 4xx uses. gt64260, mpc10x, etc could
easily follow this same model that provides a standard device info.
discovery interface. Of course, the OCP stuff in 2_4_devel is due
to be changed to match that of 2.5 is the near future...benh is
working on that.
Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-02-27 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 15:31 RFC: gt64260 descriptor struct Brian Waite
2003-02-27 16:27 ` Matt Porter [this message]
2003-02-27 18:01 ` Brian Waite
2003-02-27 21:32 ` Matt Porter
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=20030227092701.A15982@home.com \
--to=porter@cox.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=waite@skycomputers.com \
/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.