From: Jun Sun <jsun@mvista.com>
To: James Simmons <jsimmons@transvirtual.com>
Cc: Ralf Baechle <ralf@oss.sgi.com>,
Atsushi Nemoto <nemoto@toshiba-tops.co.jp>,
linux-mips@oss.sgi.com, linux-mips-kernel@lists.sourceforge.net
Subject: Re: [Linux-mips-kernel]Re: i8259.c in big endian
Date: Fri, 09 Nov 2001 10:30:45 -0800 [thread overview]
Message-ID: <3BEC20D5.AD6ABBA6@mvista.com> (raw)
In-Reply-To: Pine.LNX.4.10.10111081348000.13456-100000@transvirtual.com
James Simmons wrote:
>
> > > > The mips_io_port_base is 0xa0000000. Whereas the i8259 chip is at
> > > > 0xb0000000. The 0xa000000 value could be wrong. I will give it a try.
> > >
> > > As your board must have RAM at physical address zero 0xa0000000 is almost
> > > certainly a wrong value.
> >
> > Your right. The address of 0xb000000 is bogus. This is the value from the
> > old code. I will migrate the code over to the i8259.c stuff now. Thanks.
>
> Actually looking threw other mips branches now I see what the 0xb000000
> is. It is the isa_port_base.
>
You are probably referring to isa_slot_offset?
isa_slot_offset is an obselete garbage. Can someone do Ralf's a favor and
send him a patch to get rid of it (as if he can't do it himself :-0) ?
Jun
next prev parent reply other threads:[~2001-11-09 18:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-08 6:47 i8259.c in big endian Atsushi Nemoto
2001-11-08 17:45 ` James Simmons
2001-11-08 20:13 ` Ralf Baechle
2001-11-08 20:20 ` James Simmons
2001-11-08 20:41 ` Ralf Baechle
2001-11-08 21:37 ` James Simmons
2001-11-08 21:53 ` [Linux-mips-kernel]Re: " James Simmons
2001-11-09 18:30 ` Jun Sun [this message]
2001-11-09 18:44 ` James Simmons
2001-11-09 19:44 ` Jim Paris
2001-11-09 20:50 ` Jun Sun
2001-11-12 12:15 ` Ralf Baechle
2001-11-12 18:31 ` Jun Sun
2001-11-12 19:56 ` Florian Laws
2001-11-12 23:56 ` Ralf Baechle
2001-11-12 21:49 ` James Simmons
2001-11-09 17:41 ` Ralf Baechle
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=3BEC20D5.AD6ABBA6@mvista.com \
--to=jsun@mvista.com \
--cc=jsimmons@transvirtual.com \
--cc=linux-mips-kernel@lists.sourceforge.net \
--cc=linux-mips@oss.sgi.com \
--cc=nemoto@toshiba-tops.co.jp \
--cc=ralf@oss.sgi.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