From: David Monro <davidm@amberdata.demon.co.uk>
To: Daniel Jacobowitz <drow@false.org>
Cc: Linux/ppc Dev List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: strange PCI resource behaviour in 2.4
Date: Thu, 24 Aug 2000 20:43:40 +0100 [thread overview]
Message-ID: <39A57AEC.6FA63ED5@amberdata.demon.co.uk> (raw)
In-Reply-To: 20000823212118.A18375@false.org
Daniel Jacobowitz wrote:
>
> On Thu, Aug 24, 2000 at 02:03:19AM +0100, David Monro wrote:
> >
> > Hi,
> >
> > I'm seeing a strange problem with the PCI code on 2.4. What is happening
> > is that the PCI code seems to be detecting a memory region on my pcnet32
> > chip, but leaving it at 0x0:
> >
[snip]
> How recent a 2.4? There was a bug very like this in 2.4.0test6
> affecting all architectures as far as i know. It was resolved in the
> latest 2.4.0-test7 prepatch.
>
Problem still occurs with 2.4.0-test7-pre7 :-( I'll have to look at it
in more detail.
Cheers,
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-08-24 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-24 1:03 strange PCI resource behaviour in 2.4 David Monro
2000-08-24 2:33 ` Frank Rowand
2000-08-24 4:21 ` Daniel Jacobowitz
2000-08-24 5:59 ` David Monro
2000-08-24 19:43 ` David Monro [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=39A57AEC.6FA63ED5@amberdata.demon.co.uk \
--to=davidm@amberdata.demon.co.uk \
--cc=drow@false.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).