9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] South bridge not found
Date: Tue, 22 Oct 2002 15:59:32 +0900	[thread overview]
Message-ID: <ebadbf27f1605da0184942bcb2b93e59@granite.cias.osakafu-u.ac.jp> (raw)

[-- Attachment #1: Type: text/plain, Size: 287 bytes --]

It is vid=0x10DE did=0x0171.

I tried Russ's patch, and recompiled kernel, and got panic. :-)
Please wait for a while, I have not updated source tree for a while.
settime() is the problem (only one, I don't knwo).

After solving this problem, I'll try Russ's suggestion.

Kenji

[-- Attachment #2: Type: message/rfc822, Size: 2243 bytes --]

From: andrey mirtchovski <andrey@lanl.gov>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] South bridge not found
Date: Tue, 22 Oct 2002 00:46:13 -0600 (MDT)
Message-ID: <20021022004039.F30430-100000@fbsd.acl.lanl.gov>

On Tue, 22 Oct 2002, Russ Cox wrote:

> That makes the problem a lot easier.
>
[snip]

As usual, you have the correct solution.

What is the vendor ID for this card? It should be in the current
P9 driver already, but that means somebody actually had a card with the same
device ID and did not report a problem?

I definitely have had no such experience with the Ti4600...

andrey

             reply	other threads:[~2002-10-22  6:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22  6:59 okamoto [this message]
2002-10-22 14:34 ` andrey mirtchovski
  -- strict thread matches above, loose matches on Subject: below --
2002-10-23  1:15 Russ Cox
2002-10-23  1:04 okamoto
2002-10-22  8:09 okamoto
2002-10-22  6:29 Russ Cox
2002-10-22  6:46 ` andrey mirtchovski
2002-10-22  6:24 okamoto
2002-10-22  3:24 okamoto
2002-10-22  2:15 okamoto
2002-10-22  2:30 ` andrey mirtchovski
2002-10-21 18:01 David Gordon Hogan
2002-10-21  9:33 okamoto
2002-10-21  7:41 okamoto

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=ebadbf27f1605da0184942bcb2b93e59@granite.cias.osakafu-u.ac.jp \
    --to=okamoto@granite.cias.osakafu-u.ac.jp \
    --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).