From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Michael Ang <mang@subcarrier.org>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] State Of The Port
Date: Sat, 5 Feb 2000 15:37:59 +0100 [thread overview]
Message-ID: <20000205153759.A538@alpha.franken.de> (raw)
In-Reply-To: <Pine.BSF.4.10.10002042255350.8742-100000@cuzea.pair.com>; from Michael Ang on Fri, Feb 04, 2000 at 11:17:33PM -0500
On Fri, Feb 04, 2000 at 11:17:33PM -0500, Michael Ang wrote:
> Thomas Bogendorf
look it up in the From: line:-)
> Expects to have it working by this weekend. Lack of endianess
> support is the main problem. 2.2.14 is the "latest" tulip.c
> but has no big endian support.
the 2.2.14 tulip.c driver has big endian support as well as Donald's latest
alpha version.
> Willy mentioned that we will have to think about running on 64bit at some
> point.
IMHO, it's way too early to even think about it. Of course 64bit is sexy,
but without a working 32bit userland it's a too big can of worms to open
right now. Linux/MIPS64 hasn't started before a reasonable distribution
existed, and I'm sure this wasn't a bad descision then.
Thomas.
--
This device has completely bogus header. Compaq scores again :-|
It's a host bridge, but it should be called ghost bridge instead ;^)
[Martin `MJ' Mares on linux-kernel]
next prev parent reply other threads:[~2000-02-05 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-05 4:17 [parisc-linux] State Of The Port Michael Ang
2000-02-05 14:37 ` Thomas Bogendoerfer [this message]
2000-02-05 18:26 ` [parisc-linux] ELFness and 64bit willy
2000-02-06 2:03 ` Thomas Bogendoerfer
2000-02-08 20:15 ` [parisc-linux] " Sam Creasey
2000-02-06 1:35 ` [parisc-linux] State Of The Port Grant Grundler
[not found] <20000106210702.S5882@thepuffingroup.com>
2000-01-07 21:47 ` Matthew Wilcox
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=20000205153759.A538@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=mang@subcarrier.org \
--cc=parisc-linux@thepuffingroup.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox