From: yulin <yulin@starsoftcomm.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Uwe Koziolek <uwe.koziolek@gmx.net>,
Jeff Garzik <jeff@garzik.org>,
linux-ide@vger.kernel.org, micha.biermann@gmx.de
Subject: Re: [PATCH 2.6.22-rc4]: libata: PATA-mode fixes for sis_sata
Date: Mon, 16 Jul 2007 17:20:45 +0800 [thread overview]
Message-ID: <469B386D.8020709@starsoftcomm.com> (raw)
In-Reply-To: <20070716100401.7a0b850e@the-village.bc.nu>
Alan Cox 写道:
>> So one leader of our IT, who is a Windows expert, suggested we can use
>> int 13h and I/O in Linux. But int 13h just is used in real mode.
>>
>> Can you give me some advice to persuade him? If it is feasible, can you
>> introduce me?
>>
>
> int13 is real mode only, runs polled and 16bit with one command at a
> time. As far as I know even Windows no longer uses it for anything but
> booting.
>
>
>> Even can you give some good solutions to solve the compatibility problem?
>>
>
> For hardware where we have info the right answer is to report bugs and
> get them fixed (or indeed send fixes). For the more general case the
> ata_generic driver will drive anything that is SFF8038i compliant and you
> can just add PCI identifiers to it for anything you hit.
>
> I am working on a generic ACPI driver to go with it for such cases.
>
> Alan
>
>
>
Thank you for your help and explanations.
I will do some research work on ata_generic driver. Can you give me some
advice or related information to do deeper research?
I alse found the problem of ACPI in our product, so we turn it off, but
always caused some other problems. So i think a generic ACPI driver will
be welcome.
And your mail is the best message received today before going home.
:)
From YuLin
prev parent reply other threads:[~2007-07-16 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 21:40 [PATCH 2.6.22-rc4]: libata: PATA-mode fixes for sis_sata Uwe Koziolek
2007-07-02 14:20 ` Jeff Garzik
2007-07-16 2:34 ` yulin
2007-07-16 9:04 ` Alan Cox
2007-07-16 9:20 ` yulin [this message]
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=469B386D.8020709@starsoftcomm.com \
--to=yulin@starsoftcomm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=micha.biermann@gmx.de \
--cc=uwe.koziolek@gmx.net \
/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;
as well as URLs for NNTP newsgroup(s).