9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: venti+fossil problems on new install
Date: Thu, 21 Sep 2006 22:08:46 +0100	[thread overview]
Message-ID: <27ef1a05d9c20a587ef59bd2c59759bf@terzarima.net> (raw)
In-Reply-To: <8b2d1dd7ac49c48a0b3c0b031c6b77ff@plan9.bell-labs.com>

> Did I look at the wrong thread? I thought the original message
> showed the drives configured OK (without DMA...) but there were
> errors in the configuration steps after that. No?

no, i think that's right.  i was answering (or trying to address) erik's objection
that it was impossible for a device without its ID in the pcimatch loop to be
recognised at all.  as jmk had observed earlier, if it's at the normal address,
as the other chap's drive had been (according to the config data printed),
it will be (and was) recognised.  if it's at the normal address(es), the device
will be picked up there, SATA or not, and does not need to be handled by
the later pcimatch loop (which would ignore unlisted cards).



  reply	other threads:[~2006-09-21 21:08 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-21  6:50 John Stalker
2006-09-21  8:13 ` erik quanstrom
2006-09-21 18:19 ` Lyndon Nerenberg
2006-09-21 18:25   ` erik quanstrom
2006-09-21 18:51     ` jmk
2006-09-21 20:27       ` C H Forsyth
2006-09-21 20:47     ` Charles Forsyth
2006-09-21 20:56       ` jmk
2006-09-21 21:08         ` Charles Forsyth [this message]
2006-09-21 21:50           ` erik quanstrom
2006-09-21 22:00             ` Charles Forsyth
2006-09-21 22:16               ` erik quanstrom
2006-09-21 22:31                 ` Charles Forsyth
2006-09-21 22:31                 ` jmk
2006-09-21 23:22                   ` erik quanstrom
2006-09-21 23:28                     ` geoff
2006-09-21 23:47                       ` geoff
2006-09-22  0:05                         ` erik quanstrom
2006-09-22  0:24                           ` Russ Cox
2006-09-22  0:50                             ` erik quanstrom
2006-09-22  1:25                               ` jmk
2006-09-22  7:23                             ` John Stalker
2006-09-22 11:23                               ` erik quanstrom
2006-09-22 17:30                                 ` John Stalker
2006-09-22 17:45                                   ` erik quanstrom
2006-09-22 19:48                                     ` John Stalker
2006-09-22 20:09                                       ` erik quanstrom
2006-09-22 20:50                                         ` John Stalker
2006-09-22 21:06                                           ` erik quanstrom
2006-09-22  0:29                           ` jmk
2006-09-21 23:52                       ` erik quanstrom
2006-09-21 23:59                       ` erik quanstrom
2006-09-22  0:50                         ` geoff
2006-09-22 16:39                           ` erik quanstrom
2006-09-23  5:24 Zoran Kolic
2006-09-23  6:51 ` John Stalker
2006-09-23 10:34   ` erik quanstrom
2006-09-23 15:04     ` Russ Cox

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=27ef1a05d9c20a587ef59bd2c59759bf@terzarima.net \
    --to=forsyth@terzarima.net \
    --cc=9fans@cse.psu.edu \
    /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).