From: Pete Popov <ppopov@embeddedalley.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: PATCH
Date: Sun, 10 Oct 2004 17:39:38 -0700 [thread overview]
Message-ID: <4169D64A.9030303@embeddedalley.com> (raw)
In-Reply-To: <Pine.LNX.4.58L.0410110102440.4217@blysk.ds.pg.gda.pl>
Maciej W. Rozycki wrote:
> On Sun, 10 Oct 2004, Pete Popov wrote:
>
>
>>>If not, why not use a data type that covers
>>>valid offsets only when passing addresses to bus access functions?
>>
>>The attribute and memory pcmcia addresses are just stored in these
>>variables, and then the upper pcmcia stack layer calls ioremap on these
>>addresses. Thus, you need the 36 bit I/O address patch, as well as the
>>tiny pcmcia patch.
>>
>>The pcmcia I/O address is ioremapped at the socket driver level. If that
>>was the case with the mem and attribute addresses, I wouldn't need this
>>64 bit pcmcia patch. But since it's the upper pcmcia layer that ioremaps
>>these addresses, I need to store tham in 64 bit types.
>
>
> OK, but then phys_t should be used for ioaddr_t universally, shouldn't
> it? Any architecture can have the controller seen in a 64-bit memory
> space, after all.
Perhaps, but when I tried that in 2.4, I got rejected. Matt had an idea
that works for both, mips and ppc, since the 36 bit fixup_bigphys_addr
routine is very similar. I think I'll pursue that instead, since we
already have that routine as part of the pci address support. Thus, I
won't have to make pcmcia changes to common files, and no more
64bit_pcmcia.patch hanging around in my directory.
Pete
next prev parent reply other threads:[~2004-10-11 0:39 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 17:17 PATCH Pete Popov
2004-10-10 18:01 ` PATCH Geert Uytterhoeven
2004-10-10 19:11 ` PATCH Maciej W. Rozycki
2004-10-10 22:50 ` PATCH Pete Popov
2004-10-11 0:25 ` PATCH Maciej W. Rozycki
2004-10-11 0:39 ` Pete Popov [this message]
2004-10-10 19:33 ` PATCH Matt Porter
2004-10-10 22:52 ` PATCH Pete Popov
2004-10-10 23:41 ` PATCH Pete Popov
-- strict thread matches above, loose matches on Subject: below --
2004-10-11 0:01 PATCH Pete Popov
2004-10-11 0:32 ` PATCH Maciej W. Rozycki
2004-10-11 0:47 ` PATCH Pete Popov
2004-10-11 7:55 ` PATCH Pete Popov
2004-10-11 10:32 ` PATCH Christoph Hellwig
2004-10-11 17:07 ` PATCH Pete Popov
2004-10-11 13:53 ` PATCH Atsushi Nemoto
2004-10-11 16:33 ` PATCH Pete Popov
2004-10-11 18:04 ` PATCH Pete Popov
2004-10-10 23:43 PATCH Pete Popov
2004-10-10 7:17 PATCH Pete Popov
2004-10-10 5:31 PATCH Pete Popov
2002-12-14 4:52 PATCH Pete Popov
2002-12-17 22:29 ` PATCH Greg Lindahl
2002-12-17 22:40 ` PATCH Pete Popov
2002-12-17 23:24 ` PATCH Alan Cox
2002-12-17 22:51 ` PATCH Pete Popov
2002-12-17 22:59 ` PATCH Greg Lindahl
2002-12-20 20:43 ` PATCH James Simmons
2002-12-20 20:59 ` PATCH Pete Popov
2002-12-21 20:39 ` PATCH James Simmons
2002-12-14 4:50 PATCH Pete Popov
2002-07-15 22:29 PATCH Pete Popov
2002-07-16 15:07 ` PATCH Ralf Baechle
2002-07-16 15:15 ` PATCH Pete Popov
2002-07-16 17:43 ` PATCH Joe George
2002-07-16 18:00 ` PATCH Pete Popov
2002-07-17 0:29 ` PATCH Vivien Chappelier
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=4169D64A.9030303@embeddedalley.com \
--to=ppopov@embeddedalley.com \
--cc=geert@linux-m68k.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.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