public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: linux-ia64@vger.kernel.org
Subject: Re: build problems/questions (2.6.0-test3)
Date: Fri, 22 Aug 2003 02:25:51 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106151933415932@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106151574613417@msgid-missing>

On Thu, Aug 21, 2003 at 06:28:50PM -0700, Randy.Dunlap wrote:
> I'm seeing some build problems and want to see if they are just my
> problems.  Shoule these build OK on ia64 or are they all just
> dont-cares for ia64?
> 
> 1.  driver/block/floppy.c

Don't-care.  Should be made unselectable in Kconfig.  No ia64 boxes have
shipped with that kind of floppy drive (ide-floppy on the first boxes).

> 2.  drivers/char/nvram.c ?? (x86-ism)

I doubt anyone put an mc146818rtc chip in an ia64 box.

> 3.  drivers/char/hangcheck.c ?

Do you mean drivers/char/hangcheck-timer.c?  This looks x86-specific to me,
monotonic_clock() is in arch/i386 and arch/x86_64 only.

> 4.  ISA PNP support?

Definitely no ISA on these boxes.  Shouldn't ISAPNP depend on ISA in Kconfig?

-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk

  reply	other threads:[~2003-08-22  2:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-22  1:28 build problems/questions (2.6.0-test3) Randy.Dunlap
2003-08-22  2:25 ` Matthew Wilcox [this message]
2003-08-22  4:46 ` Randy.Dunlap
2003-08-22 14:43 ` David Mosberger
2003-08-22 18:54 ` Randy.Dunlap
2003-08-22 21:57 ` Randy.Dunlap
2003-08-23  2:05 ` David Mosberger

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=marc-linux-ia64-106151933415932@msgid-missing \
    --to=willy@debian.org \
    --cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox