Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Grant Grundler <grundler@dsl2.external.hp.com>
Cc: Christian Suder <csuder@cisco.com>, Helge Deller <deller@gmx.de>,
	parisc-linux@lists.parisc-linux.org
Subject: Re: Fwd: Re: [parisc-linux] [Q] on EISA support
Date: Thu, 27 Dec 2001 23:45:56 +0100	[thread overview]
Message-ID: <20011227234556.A7543@solo.franken.de> (raw)
In-Reply-To: <20011227195930.446D54861@dsl2.external.hp.com>; from grundler@dsl2.external.hp.com on Thu, Dec 27, 2001 at 12:59:30PM -0700

On Thu, Dec 27, 2001 at 12:59:30PM -0700, Grant Grundler wrote:
> Christian Suder wrote:
> > the entry is in the .config file. I'll try -pa27 later, there seem to be 
> > some issues with the -pa25 in general,
> 
> Yes - I broke dino (PCI) support in -pa25 when I re-enabled c3000 machines.
> I might have also broke EISA support but don't think so.

EISA is broken for ccio machines (ok, only checked on my C200), because
ccio requests memory space, which the eisa part wants too. I have it
"working" again, but the patch is definitly not for common use. The big
problem is, that ccio registers a primary and secondary memory space,
but ccio_find_parisc_resource() only gives back the resource for the
primary gsc space, which is the wrong one.

> Thomas fixed that in -pa26 (or pa27?).

-pa26

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:[~2001-12-27 22:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4.3.2.7.2.20011227103742.02a018e8@mira-sjc5-9.cisco.com>
2001-12-27 18:49 ` Fwd: Re: [parisc-linux] [Q] on EISA support Christian Suder
2001-12-27 19:59   ` Grant Grundler
2001-12-27 22:45     ` Thomas Bogendoerfer [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=20011227234556.A7543@solo.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=csuder@cisco.com \
    --cc=deller@gmx.de \
    --cc=grundler@dsl2.external.hp.com \
    --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