linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: "Gaston, Jason D" <jason.d.gaston@intel.com>
Cc: Jeff Garzik <jeff@garzik.org>, linux-ide@vger.kernel.org
Subject: Re: Unknown SATA PIIX PCI device ID 0x29b6
Date: Wed, 23 Apr 2008 15:37:02 +0900	[thread overview]
Message-ID: <480ED90E.1080300@gmail.com> (raw)
In-Reply-To: <39B20DF628532344BC7A2692CB6AEE070294E62F@orsmsx420.amr.corp.intel.com>

Gaston, Jason D wrote:
>>> IDER is a controller, in this case, in the MCH/Northbridge that
>>> redirects a virtual drive across the LAN and presents it as 
>> a local IDE
>>> drive.  This is part of the Intel AMT manageability engine.  You can
>>> point it to a physical drive, .iso or a .img file on the 
>> remote system.
>>
>> Ah... fancy.  You can just make it PATA if doesn't have SCR access and 
>> supports slave device and use ata_cable_unknown() for ->cbl_detect.
>>
>> -- 
>> tejun
>>
> 
> After messing around for a bit, what I came up with that worked, was
> very similar to what it set for ich8_sata_ahci.  So, I tried just adding
> the new DeviceID as an ich8_sata_ahci and it seems to work fine.  Do you
> see anything wrong with just doing this?  I'm not sure that the port map
> is relevant for a virtual device?  I have attached the dmesg output for
> your review.

Things look fine to me but I think it's probably best to create a 
separate port info entry for it.  Is SIDPR available for IDER too?

-- 
tejun

  reply	other threads:[~2008-04-23  6:37 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-28 22:37 Unknown SATA PIIX PCI device ID 0x29b6 Guennadi Liakhovetski
2008-02-28 22:56 ` Alan Cox
2008-02-28 23:33   ` Guennadi Liakhovetski
2008-03-06  8:39     ` Tejun Heo
2008-03-06 11:57       ` Guennadi Liakhovetski
2008-03-06 18:02         ` Gaston, Jason D
2008-03-06 18:05           ` Jeff Garzik
2008-03-06 18:40             ` Guennadi Liakhovetski
2008-04-02 23:49             ` Gaston, Jason D
2008-04-03  0:44               ` Tejun Heo
2008-04-03 15:16                 ` Gaston, Jason D
2008-04-03 16:03                   ` Tejun Heo
2008-04-19  1:02                     ` Gaston, Jason D
2008-04-23  6:37                       ` Tejun Heo [this message]
2008-04-03 16:04                   ` Jeff Garzik
2008-04-03 18:01                     ` Gaston, Jason D
2008-03-07  4:51         ` Tejun Heo
2008-03-08 22:47           ` Guennadi Liakhovetski
2008-03-09  5:14             ` Tejun Heo
2008-03-09 21:24               ` Guennadi Liakhovetski
2008-03-10  0:50                 ` Tejun Heo
2008-03-10  7:22                   ` Guennadi Liakhovetski
2008-03-10 13:05                     ` Tejun Heo
2008-03-11 10:11                       ` Guennadi Liakhovetski
2008-03-11 10:35                         ` Tejun Heo
2008-03-11 11:13                           ` Guennadi Liakhovetski
2008-03-11 11:37                             ` Tejun Heo
2008-02-29  0:23   ` Felix Miata
2008-02-29  3:50     ` Gaston, Jason D

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=480ED90E.1080300@gmail.com \
    --to=htejun@gmail.com \
    --cc=jason.d.gaston@intel.com \
    --cc=jeff@garzik.org \
    --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 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).