All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@mvista.com>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org, Deepak Saxena <dsaxena@mvista.com>
Subject: Re: PCI SATA controllers on embedded, no-BIOS targets
Date: Tue, 22 Aug 2006 10:37:30 -0700	[thread overview]
Message-ID: <44EB40DA.3010904@mvista.com> (raw)
In-Reply-To: <44EB3F70.6000702@gmail.com>

Tejun Heo wrote:
> Tejun Heo wrote:
>> Kevin Hilman wrote:
>>> Tejun Heo wrote:
>>>> Kevin Hilman wrote:
>>>>> I have a Silicon Images 3112 PCI card on an XScale IXP425 
>>>>> platform.  The card works well in a PC, but I haven't got it to 
>>>>> work in on the ARM platform.  On the PC, I see the cards BIOS 
>>>>> executed and am guessing that since this can't happen on the ARM, 
>>>>> that's why things aren't working.
>>>>>
>>>>> The card is at least detected on the ARM, and the driver tries to 
>>>>> probe for devices, but times out an moves on.
>>>>>
>>>>> Before I debug this too deeply, I want to make sure this should 
>>>>> work on embedded boards, even without the BIOS execution.
>>>>
>>>> sil3112 works fine w/o any BIOS initialization.
>>>>
>>>
>>> I'm curious what platforms this has been tested.  Any non-x86 
>>> platforms?  Any big endian platforms?
>>>
>>> Thanks for the quick response.
>>
>> I've personally seen it working on XScale and ATI's mips.

OK, that's good to know.

> For the record, for ATI's new mips platform, sata_sil needs some 
> modifications.  Their PCI bridge can't handle byte-aligned mmio and the 
> driver had to be modified to use IO address space.

I'm using 2.6.18-rc4 on this XScale IXP425 (big endian) and both the 
legacy driver (drivers/ide/pci/siimage.c) and the libata driver 
(drivers/scsi/sata_sil.c) cause crashes during probing due to bad memory 
accesses.

Switching the legacy driver into PIO mode makes the probing work well, 
but still can't figure out what's happening in the libata driver, AFICT, 
it can't do PIO.

Any chance you can share the changes to use IO address space?  Maybe the 
PCI on this XScale has similar limitations.

Kevin

  reply	other threads:[~2006-08-22 17:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-22 16:37 PCI SATA controllers on embedded, no-BIOS targets Kevin Hilman
2006-08-22 16:41 ` Tejun Heo
2006-08-22 16:52   ` Kevin Hilman
2006-08-22 17:26     ` Tejun Heo
2006-08-22 17:31       ` Tejun Heo
2006-08-22 17:37         ` Kevin Hilman [this message]
2006-08-22 18:00           ` Tejun Heo
2006-08-22 18:02             ` Tejun Heo
2006-08-22 21:58             ` Kevin Hilman
2006-08-23  3:24               ` Tejun Heo
2006-08-23  3:52                 ` Tejun Heo
2006-09-07 23:05                 ` Kevin Hilman
2006-09-08  1:46                   ` Jeff Garzik
2006-09-08  7:27                     ` Tejun Heo
2006-09-08 12:00                       ` Jeff Garzik
2006-09-08 16:29                       ` Kevin Hilman
2006-09-08 16:40                         ` Sergei Shtylyov

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=44EB40DA.3010904@mvista.com \
    --to=khilman@mvista.com \
    --cc=dsaxena@mvista.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.