All of lore.kernel.org
 help / color / mirror / Atom feed
From: "mirabilos" <eccesys@topmail.de>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>,
	"Jeff Garzik" <jgarzik@mandrakesoft.com>
Cc: "Pavel Roskin" <proski@gnu.org>,
	"Pete Zaitcev" <zaitcev@redhat.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Patch to make ymfpci legacy address 16 bits
Date: Thu, 10 May 2001 11:54:48 -0000	[thread overview]
Message-ID: <00a501c0d948$1c6b4a40$de00a8c0@homeip.net> (raw)
In-Reply-To: <200105100253.f4A2rsK305959@saturn.cs.uml.edu>

> When you write "the kernel", do you mean the driver or generic
> code? I hope you mean the driver, because I have this:
> 
> 1. the device looks normal at power on
> 2. the driver pokes a device-specific config register
> 3. the config space header changes from type 0 to type 1
> 
> (The class code does NOT indicate PCI-to-PCI bridge.
> You could say this is like CardBus but much weirder)
> 
> If the kernel saves type 1 header data, cuts power using
> motherboard features, restores power, and then tries to
> restore type 1 header data into a type 0 header... the
> system will be well and truly screwed IMHO.

This reminds me of being unable to use my sound card under Windoze
after stand-by, suspend etc. (NB Win2k hibernate worked, suspend
I had disabled then).
Seems as not only linux has this kind of problems...
I don't remember _which_ card it was but I am quite sure it was
an old OPTi MAD16 Pro.

-mirabilos
-- 
EA F0 FF 00 F0 #$@%CARRIER LOST


  parent reply	other threads:[~2001-05-10 11:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-09 20:17 Patch to make ymfpci legacy address 16 bits Pavel Roskin
2001-05-09 20:23 ` Jeff Garzik
2001-05-09 20:52   ` Pavel Roskin
2001-05-09 21:08     ` Jeff Garzik
2001-05-09 23:43       ` Pavel Roskin
2001-05-09 23:53       ` Zach Brown
2001-05-10  2:53   ` Albert D. Cahalan
2001-05-10  7:28     ` Question: Status of USAGI/FreeSWAN? Dax Kelson
2001-05-11  2:52       ` Mike Fedyk
2001-05-10 11:54     ` mirabilos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-09  0:37 Patch to make ymfpci legacy address 16 bits Pete Zaitcev

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='00a501c0d948$1c6b4a40$de00a8c0@homeip.net' \
    --to=eccesys@topmail.de \
    --cc=acahalan@cs.uml.edu \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=proski@gnu.org \
    --cc=zaitcev@redhat.com \
    /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.