public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Steinmetz <ast@domdv.de>
To: John Bradford <john@grabjohn.com>
Cc: Pete Zaitcev <zaitcev@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Sparc IDE in 2.4.20
Date: Fri, 14 Feb 2003 23:49:59 +0100	[thread overview]
Message-ID: <3E4D7297.8060200@domdv.de> (raw)
In-Reply-To: <200302142131.h1ELVX4U004986@darkstar.example.net>

John Bradford wrote:
>>>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.
> 

Got a nifty little SunBlade 100 on my desk at work, though it is running 
Solaris. This system has IDE disks so there must be more than one IDE 
capable Sparc on this planet :-)
-- 
Andreas Steinmetz


  reply	other threads:[~2003-02-14 22:40 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
2003-02-14 22:49     ` Andreas Steinmetz [this message]
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=3E4D7297.8060200@domdv.de \
    --to=ast@domdv.de \
    --cc=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