public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Komuro <komurojun-mbn@nifty.com>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: libata reports bogus addresses for everything (was PATA_PCMCIA cmd port)
Date: Sun, 18 Mar 2007 14:48:31 +0900	[thread overview]
Message-ID: <45FCD2AF.90909@gmail.com> (raw)
In-Reply-To: <20070317154333.088d77d4@lxorguk.ukuu.org.uk>

Alan Cox wrote:
> On Sat, 17 Mar 2007 22:00:50 +0900
> Komuro <komurojun-mbn@nifty.com> wrote:
> 
>> Hi,
>>  
>> The pata_pcmcia driver reports the cmd port is 0x00010100,
>> but actually the cmd port is 0x0100.
>>
>> Is this corect?
> 
> When the pci_iomap patches were applied the ports reported for every
> device went strange.  It appears to display the wrong information
> nowdays. I see the same but I've got many more important things to work
> on before I even bother to look at it.
> 
> My guess is someone is now printing the iomap virtual addresses not the
> bus ones.

Yes, we're printing the ioaddr.* directly and those are all iomapped
addressed now.  I wonder whether we should fix this or push the port
printing to LLDs (with sff helpers in libata-sff).  ahci and
pata_generic sharing one format doesn't sound like a too good idea.
I'll fix it after new init model.

-- 
tejun

  reply	other threads:[~2007-03-18  5:48 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-17 12:27 [BUG KERNEL 2.6.20-rc1] ftp: get or put stops during file-transfer Komuro
2006-12-17  4:02 ` Al Viro
2006-12-17 14:23   ` Komuro
2006-12-18  3:01     ` Adrian Bunk
2006-12-18 20:55       ` Komuro
2006-12-23 11:17       ` Komuro
2006-12-30  9:50       ` Komuro
2006-12-30  1:23         ` YOSHIFUJI Hideaki / 吉藤英明
2006-12-30 11:59           ` Komuro
2006-12-30 14:19             ` YOSHIFUJI Hideaki / 吉藤英明
2006-12-31  9:42               ` Komuro
2007-01-01 17:18               ` Komuro
2007-01-04 20:45               ` Komuro
2007-01-04 12:23                 ` Craig Schlenter
2007-01-09  1:24                   ` YOSHIFUJI Hideaki / 吉藤英明
2007-01-09  5:11                     ` [PATCH] " Craig Schlenter
2007-01-09  5:22                       ` YOSHIFUJI Hideaki / 吉藤英明
2007-01-09  8:11                         ` David Miller
2007-01-09 22:01                   ` Komuro
     [not found]   ` <20070211101537.e40fa309.komurojun-mbn@nifty.com>
2007-02-11  1:56     ` [BUG] PATA_PCMCIA does not work Alan
2007-02-11 10:32       ` Haavard Skinnemoen
2007-02-11  2:40     ` Komuro
2007-02-18  2:09       ` Komuro
2007-02-21 15:37         ` Alan
2007-02-21 15:24           ` Manuel Lauss
2007-02-24  2:06           ` Komuro
2007-02-24 23:14           ` Komuro
2007-02-25  1:45             ` Jeff Garzik
2007-02-25  2:43               ` Komuro
2007-03-21  1:56           ` [PATCH]: pcmcia - spot slave decode flaws (for testing) Komuro
2007-03-17 13:00     ` [BUG] PATA_PCMCIA cmd port Komuro
2007-03-17 15:43       ` libata reports bogus addresses for everything (was PATA_PCMCIA cmd port) Alan Cox
2007-03-18  5:48         ` Tejun Heo [this message]
2007-03-17 16:10       ` [BUG] PATA_PCMCIA cmd port Jeff Garzik

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=45FCD2AF.90909@gmail.com \
    --to=htejun@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=komurojun-mbn@nifty.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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