All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabian Knittel <fabian.knittel@avona.com>
To: Milan Kupcevic <milan@physics.harvard.edu>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Eyal Lebedinsky <eyal@eyal.emu.id.au>,
	Stan Seibert <volsung@mailsnare.net>,
	linux-ide@vger.kernel.org,
	Christiaan den Besten <chris@scorpion.nl>
Subject: Re: [PATCH] sata_promise: Port enumeration order - SATA 150 TX4, SATA 300 TX4
Date: Tue, 06 Jun 2006 19:27:17 +0200	[thread overview]
Message-ID: <4485BAF5.9060507@avona.com> (raw)
In-Reply-To: <447CB9B4.50700@physics.harvard.edu>

Milan Kupcevic wrote:
> Please respond with this data:
> 
> - Your Promise SATA controller retail name
> - Chip label (PDCxxxxx)
> - PCI vendor and device code as you can get with "lspci -n"
> - Say if the controler has the new or the old wiring

We only have one card and it matches one of yours:

  Retail name: SATAII150 TX4
  Chip label: PDC40518  SATAII150
  Vendor-Device number: 105a:3d18 (rev 02)
  Wiring: NEW

Greetings, Fabian
-- 
avona media GbR      | Neureuter Str. 5-7   | D-76185 Karlsruhe
fon +49 721 53169901 | fax +49 721 53169904 | www.avona.com

  reply	other threads:[~2006-06-06 17:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-25  1:09 [PATCH] sata_promise: Port enumeration order - SATA 150 TX4, SATA 300 TX4 Milan Kupcevic
2006-02-25  1:16 ` Jeff Garzik
2006-02-25  1:42   ` Milan Kupcevic
2006-02-25  6:59 ` Eyal Lebedinsky
2006-02-25 10:52   ` Christiaan den Besten
2006-02-25 10:52     ` Christiaan den Besten
2006-03-31 22:52     ` Fabian Knittel
2006-05-30 21:31       ` Milan Kupcevic
2006-06-06 17:27         ` Fabian Knittel [this message]
2006-10-02 22:08         ` Evan Harris
2006-12-16 17:09           ` Jeff Garzik
2006-02-26 19:55 ` Oliver Joa
2006-02-26 19:56 ` Oliver Joa
  -- strict thread matches above, loose matches on Subject: below --
2009-10-03 22:12 Walter Hutchins
2009-10-05 10:49 ` Mikael Pettersson

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=4485BAF5.9060507@avona.com \
    --to=fabian.knittel@avona.com \
    --cc=chris@scorpion.nl \
    --cc=eyal@eyal.emu.id.au \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=milan@physics.harvard.edu \
    --cc=volsung@mailsnare.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 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.