Linux PARISC architecture development
 help / color / mirror / Atom feed
From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
To: Grant Grundler <grundler@parisc-linux.org>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
	PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] proposed changes to dino.c
Date: Fri, 12 Dec 2003 12:30:25 +0100	[thread overview]
Message-ID: <20031212113025.GA4814@solo.franken.de> (raw)
In-Reply-To: <20031212074838.GA16885@colo.lackof.org>

On Fri, Dec 12, 2003 at 12:48:38AM -0700, Grant Grundler wrote:
> On Wed, Dec 10, 2003 at 04:54:24PM -0500, James Bottomley wrote:
> > +/* The alignment contraints for PCI bridges under dino */
> > +#define DINO_BRIDGE_ALIGN 0x100000
> 
> hrmm...I was expecting this to be defined in include/linux/pci.h
> but it's not. "pbus_size_mem()" seems to take care of this
> in the drivers/pci generic code.
> 
> > +		/* null out the ROM resource if there is one (we don't
> > +		 * care about an expansion rom on parisc, since it
> > +		 * usually contains (x86) bios code) */
> > +		dev->resource[PCI_ROM_RESOURCE].flags = 0;
> > +		dev->resource[PCI_ROM_RESOURCE].start = 0;
> > +		dev->resource[PCI_ROM_RESOURCE].end = 0;
> 
> I just realized some drivers may need to access data (not code)
> in the ROM. I'm not aware of any but I don't want to under
> estimate how creative people can get. Just something to beware
> when bringing up new cards.

doesn't this also break PCI Vis-EG and FX cards setup ? On these
cards the ROM contains PARISC firmware, which we need.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea.                                 [ Alexander Viro on linux-kernel ]

  reply	other threads:[~2003-12-12 11:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-10  4:37 [parisc-linux] proposed changes to dino.c James Bottomley
2003-12-10  4:54 ` Grant Grundler
2003-12-10 15:12   ` James Bottomley
2003-12-10 21:54   ` James Bottomley
2003-12-12  7:48     ` Grant Grundler
2003-12-12 11:30       ` Thomas Bogendoerfer [this message]
2003-12-12 15:00         ` James Bottomley
2003-12-12 15:38           ` Thomas Bogendoerfer
2003-12-12 14:58       ` James Bottomley
2003-12-12 19:28         ` Alan Cox
2003-12-13  3:51           ` Grant Grundler
2003-12-13 15:33             ` Alan Cox
2003-12-13 15:45               ` James Bottomley
2003-12-13 20:33                 ` Matthew Wilcox
2003-12-13 20:52                   ` Grant Grundler
2003-12-13  3:53           ` Grant Grundler

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=20031212113025.GA4814@solo.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=James.Bottomley@steeleye.com \
    --cc=grundler@parisc-linux.org \
    --cc=parisc-linux@lists.parisc-linux.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