Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Michael S.Zick <mszick@pflash.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Richard Hirst <rhirst@linuxcare.com>,
	debian-hppa@lists.debian.org, parisc-linux@thepuffingroup.com,
	parisc-linux@parisc-linux.org
Subject: [parisc-linux] Re: pa-risc V0.9 on Model 720 (+ others)
Date: Tue, 5 Jun 2001 12:56:29 -0500	[thread overview]
Message-ID: <01060513071704.00472@wolf01.my.home> (raw)
In-Reply-To: 20010605185008.R7349@parcelfarce.linux.theplanet.co.uk

On Tue, 05 Jun 2001, Matthew Wilcox wrote:
> On Tue, Jun 05, 2001 at 11:36:37AM -0500, Michael S. Zick wrote:
> > Without either BA's defined - in/out Byte, Word, Long does not have
> > a prototype in mem.c (amoung other places) - the compiler guesses
> > (incorrectly) at what inb() and outb() mean.
>=20
> That's a known-bad configuration.  You have to have some kind of PCI
> or EISA controller configured in.

Only if you intend to never support non-PCI, non-EISA older boxes.

Regardless of your intent - proper combinations of CONFIG_xxxxx
are supposed to be handled by the (x)config step of the build process.
After all - that is what "configure" means (in English).

To do a clean job of this - a selection of "Box Model" (similar to "Proce=
ssor Type")
may have to be added to the configuration scripts.  With corresponding #i=
fdef/#ifndef
statements in the relavent code.

At the moment - I have tunnel vision - I am focused on getting a personal=
 copy
of parisc-linux to boot on my model 720 box.

The comments and findings I post to the mailing lists may be freely disre=
garded
by anyone not interested them.  Still, they will exist in the mail list a=
rchives so that
any developer working on a public version of this kernel can use them for=
 hints, leads
and other ideas.

Mike
>=20
> --=20
> Revolutions do not require corporate support.

      reply	other threads:[~2001-06-05 18:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-04 19:16 [parisc-linux] D310 boot messages djweis
2001-06-04 21:45 ` Michael S.Zick
2001-06-04 22:09   ` djweis
2001-06-05  9:46 ` Richard Hirst
2001-06-05 12:26   ` djweis
2001-06-05 13:51     ` Richard Hirst
2001-06-05 14:14       ` djweis
2001-06-05 15:06         ` Richard Hirst
2001-06-05 15:32           ` djweis
2001-06-05 15:53           ` djweis
2001-06-05 20:59             ` Grant Grundler
2001-06-06 11:53               ` djweis
2001-06-06 14:14                 ` Grant Grundler
2001-06-05 16:36           ` [parisc-linux] pa-risc V0.9 on Model 720 (+ others) Michael S.Zick
2001-06-05 17:50             ` [parisc-linux] " Matthew Wilcox
2001-06-05 17:56               ` Michael S.Zick [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=01060513071704.00472@wolf01.my.home \
    --to=mszick@pflash.com \
    --cc=debian-hppa@lists.debian.org \
    --cc=matthew@wil.cx \
    --cc=parisc-linux@parisc-linux.org \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=rhirst@linuxcare.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