From: John Bradford <john@grabjohn.com>
To: zaitcev@redhat.com (Pete Zaitcev)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Sparc IDE in 2.4.20
Date: Fri, 14 Feb 2003 21:31:32 +0000 (GMT) [thread overview]
Message-ID: <200302142131.h1ELVX4U004986@darkstar.example.net> (raw)
In-Reply-To: <200302142106.h1EL6Do29394@devserv.devel.redhat.com> from "Pete Zaitcev" at Feb 14, 2003 04:06:13 PM
> > Is IDE known to be broken on Sparc in 2.4.20? I just got this compile
> > failiure:
> > sparc-linux-ld -T arch/sparc/vmlinux.lds arch/sparc/kernel/head.o
> > arch/sparc/kernel
> > drivers/ide/idedriver.o: In function `ide_end_drive_cmd':
> > drivers/ide/idedriver.o(.text+0x11d4): undefined reference to `inw_p'
>
> I tested it in 2.4.7 for the last time. It probably bitrotted.
> Why do you care? I posess the only IDE capable sparc on this planet.
> Just configure it out, and be happy.
I'm thinking of building a machine based around Sun's Netra AX-1105
motherboard, which I thought had a supported IDE controller built in,
but I could be wrong.
> Are you sure you did not want to compile for sparc64, hint, hint?
Oh, I'm just testing my newly compiled Sparc cross compiler :-), I
will be compiling for sparc64 eventually. I've decided not to use any
Linux distribution on the new box, and instead just to build it up
from scratch, but at the moment, I'm still trying to build a native
Sparc GCC on an X86 box, (as opposed to a cross-compiler).
John.
next prev parent reply other threads:[~2003-02-14 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1045255810.17251.linux-kernel2news@redhat.com>
2003-02-14 21:06 ` Sparc IDE in 2.4.20 Pete Zaitcev
2003-02-14 21:31 ` John Bradford [this message]
2003-02-14 22:49 ` Andreas Steinmetz
2003-02-15 11:59 ` Henning P. Schmiedehausen
2003-02-14 20:55 Holzrichter, Bruce
-- strict thread matches above, loose matches on Subject: below --
2003-02-14 20:41 John Bradford
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=200302142131.h1ELVX4U004986@darkstar.example.net \
--to=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.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