From: Jay Estabrook <Jay.Estabrook@hp.com>
To: Thomas Evans <evans02472@gmail.com>
Cc: Tejun Heo <htejun@gmail.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: sata_sil24 / Alpha / 4726 PMP issue ..
Date: Fri, 25 Jan 2008 13:16:39 -0500 [thread overview]
Message-ID: <479A2787.5000106@hp.com> (raw)
In-Reply-To: <479A2374.6080100@gmail.com>
Thomas Evans wrote:
> Saw something that caught my attention might be nothing ...
>
> When initialized, the port address is a 64 bit address:
> sil24_init_one init_one: port:FFFFFD00:09AA0000
> sil24_init_one init_one: port:FFFFFD00:09AA2000
> sil24_init_one init_one: port:FFFFFD00:09AA4000
> sil24_init_one init_one: port:FFFFFD00:09AA6000
These are KSEG addresses used for getting at the memory/registers
on the card, and were created by doing ioremap(physaddr).
> When the description from ata_port_pbar_desc comes out, it shows:
> ata13: SATA max UDMA/100 host m128@0x9aa9000 port 0x9aa0000 irq 31
> ata14: SATA max UDMA/100 host m128@0x9aa9000 port 0x9aa2000 irq 31
> ata15: SATA max UDMA/100 host m128@0x9aa9000 port 0x9aa4000 irq 31
> ata16: SATA max UDMA/100 host m128@0x9aa9000 port 0x9aa6000 irq 31
These are the physical addresses of the memory/registers of the card
on the PCI bus.
> I don't think the output is being truncated?
Nope, not truncated, just diff between physical and KSEG
> Is there some issue with the address?
Don't think so, at this time.
> ...tom
>
>
> Thomas Evans wrote:
>> added some more printk's based on what I saw -
>> maybe some issue with the dma port?
>>
>> ...tom
>>
>
next prev parent reply other threads:[~2008-01-25 18:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4794459C.3090200@gmail.com>
2008-01-21 7:26 ` sata_sil24 / Alpha / 4726 PMP issue Tejun Heo
2008-01-21 16:42 ` Thomas Evans
2008-01-21 16:47 ` Thomas Evans
2008-01-22 2:26 ` Tejun Heo
2008-01-23 4:34 ` Thomas Evans
2008-01-23 6:18 ` Tejun Heo
2008-01-24 0:22 ` Thomas Evans
2008-01-24 1:42 ` Tejun Heo
[not found] ` <864c1e490801231823v3e9cf61ds2a0d553ed5b61fb2@mail.gmail.com>
2008-01-24 2:32 ` Tejun Heo
2008-01-24 3:39 ` Thomas Evans
2008-01-24 3:52 ` Tejun Heo
2008-01-24 15:07 ` Thomas Evans
2008-01-24 15:11 ` Tejun Heo
2008-01-24 16:40 ` Thomas Evans
2008-01-24 17:08 ` Tejun Heo
[not found] ` <4798CA71.20707@gmail.com>
[not found] ` <4798CC90.4040707@gmail.com>
[not found] ` <4798CCDF.9070305@gmail.com>
[not found] ` <4798CE10.2050005@gmail.com>
[not found] ` <4798D4A2.7030303@gmail.com>
[not found] ` <47991AD9.6050804@gmail.com>
[not found] ` <47993686.5040405@gmail.com>
[not found] ` <479939E3.4020307@gmail.com>
2008-01-25 6:04 ` Thomas Evans
2008-01-25 17:28 ` Thomas Evans
2008-01-25 17:59 ` Thomas Evans
2008-01-25 18:16 ` Jay Estabrook [this message]
2008-01-27 22:50 ` Thomas Evans
2008-01-28 0:44 ` Tejun Heo
2008-01-28 6:51 ` Thomas Evans
2008-01-29 4:00 ` Thomas Evans
2008-01-29 4:24 ` Tejun Heo
2008-01-29 4:31 ` Thomas Evans
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=479A2787.5000106@hp.com \
--to=jay.estabrook@hp.com \
--cc=evans02472@gmail.com \
--cc=htejun@gmail.com \
--cc=linux-ide@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 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.