From: "Ian K. Erickson" <ian@ns0.ipeg.com>
To: "Jens Ch. Restemeier" <jenschrr@post.uni-bielefeld.de>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: BUG: 2.2.0-pre2 on 5500 (and maybe 6500)
Date: Fri, 1 Jan 1999 16:47:19 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.3.96.990101164529.9762C-100000@ns0.ipeg.com> (raw)
In-Reply-To: <368CDBC4.366C@post.uni-bielefeld.de>
On Fri, 1 Jan 1999, Jens Ch. Restemeier wrote:
> P.S.: Patch ? I'd like to, but I have not much information about the
> hardware. What about starting a project to document all devices in a Mac
I'll second that. There may be legal issue (NDAs?) involved in having
linuxppc share some hardware info, but I hope I am wrong.
Ian K. Erickson iPEG, the Internet Productivity Group
Systems Administator W 422 Riverside, Suite 628
ian@ipeg.com Spokane, WA 99204
http://www.ipeg.com (509)462-iPEG
4F6E65204F5320746F2072756C65207468656D20616C6C2C204F6E65204F5320746
F2066696E64207468656D2CDA4F6E65204F5320746F206272696E67207468656D20
616C6C20616E6420696E20746865206461726B6E6573732062696E64207468656D
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
prev parent reply other threads:[~1999-01-02 0:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-01 14:29 BUG: 2.2.0-pre2 on 5500 (and maybe 6500) Jens Ch. Restemeier
1999-01-01 19:44 ` Tom Rini
1999-01-02 9:31 ` Jens Ch. Restemeier
1999-01-02 0:47 ` Ian K. Erickson [this message]
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=Pine.LNX.3.96.990101164529.9762C-100000@ns0.ipeg.com \
--to=ian@ns0.ipeg.com \
--cc=jenschrr@post.uni-bielefeld.de \
--cc=linuxppc-dev@lists.linuxppc.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.