From: "Douglas T. Crosher" <dtc@scieneer.com>
To: rbradetich@uswest.net
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] J2240?
Date: Thu, 17 May 2001 01:17:58 +1000 [thread overview]
Message-ID: <3B029A26.7323124B@scieneer.com> (raw)
In-Reply-To: 20010515231519.A32007@beavis.ybsoft.com
Ryan Bradetich wrote:
...
> I had a chance to chat with Grant, and we have a couple of ideas, but
> we need some more info first. Grant says the IO_ADDR_EN is supposed
> to be set by the PDC ... but if no devices exist on the PCI bus below
> the dino, it is possible the IO_ADDR_EN could be 0. If this is the
> case, then we need to move the BUG() to a different spot in code.
...
> I have attached a small patch that will hopefully confirm our thoughts
> about the IO_ADDR_EN BUG() that I hope you will try out and report
> back the results. And hopefully someone is working on providing
> rs232 port support for the dino/cujo busses.
Here is the relevant output with you patch applied:
...
Dino version 3.1 (bridge mode) found at 0xfc004000
dino_bridge_init() addr: fc004000 hver: 0x680 sver: 0xa io_addr: 0x2000000
Dino version J2240 (bridge mode) found at 0xfc000000
dino_bridge_init() addr: fc000000 hver: 0x5d sver: 0xa io_addr: 0x0
...
Thanks for looking into it.
Regards
Douglas Crosher
next prev parent reply other threads:[~2001-05-16 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-13 5:45 [parisc-linux] J2240? Douglas T. Crosher
2001-05-13 18:23 ` Ryan Bradetich
2001-05-13 19:33 ` Douglas T. Crosher
2001-05-13 20:14 ` Ryan Bradetich
2001-05-16 5:15 ` Ryan Bradetich
2001-05-16 15:17 ` Douglas T. Crosher [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-12 9:18 [parisc-linux] hardware features of 712-60 ? kenneth westelinck
2002-10-15 3:35 ` [parisc-linux] J2240? Derek Engelhaupt
2002-10-15 11:28 ` Matthew Wilcox
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=3B029A26.7323124B@scieneer.com \
--to=dtc@scieneer.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=rbradetich@uswest.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.