From: Juergen Sawinski <juergen.sawinski@mpimf-heidelberg.mpg.de>
To: Pozsar Balazs <pozsy@sch.bme.hu>
Cc: "linux-kernel@vger" <linux-kernel@vger.kernel.org>
Subject: Re: Unknown bridge resource
Date: 13 Dec 2001 03:52:48 +0100 [thread overview]
Message-ID: <1008211968.16830.1.camel@nc1701d> (raw)
In-Reply-To: <Pine.GSO.4.30.0112130004310.5686-100000@balu>
In-Reply-To: <Pine.GSO.4.30.0112130004310.5686-100000@balu>
If the pci id is not found (see drivers/pci/pci.ids), you'll get this
message. If you can supply the description, the maintainer is Martin
Mares <mj@ucw.cz>, see also http://pciids.sf.net/.
On Thu, 2001-12-13 at 00:08, Pozsar Balazs wrote:
>
> Hi all,
>
> During boot, i got these two lines in dmesg:
> Unknown bridge resource 0: assuming transparent
> Unknown bridge resource 2: assuming transparent
>
> What do they mean?
>
>
> ps: I noticed these because they are written on the console even if quiet
> mode is on. There was a patch for 2.4-ac, but it seems that it somehow
> lost... :(
>
> --
> Balazs Pozsar
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Juergen Sawinski
Max-Planck-Institute for Medical Research
Dept. of Biomedical Optics
Jahnstr. 29
D-69120 Heidelberg
Germany
Phone: +49-6221-486-309
Fax: +49-6221-486-325
priv.
Phone: +49-6221-418 848
Mobile: +49-171-532 5302
next prev parent reply other threads:[~2001-12-13 2:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 23:08 Unknown bridge resource Pozsar Balazs
2001-12-13 0:36 ` Edward Muller
2001-12-13 2:52 ` Juergen Sawinski [this message]
2001-12-13 7:26 ` Pozsar Balazs
2001-12-13 23:14 ` Edward Muller
-- strict thread matches above, loose matches on Subject: below --
2001-12-05 21:41 Unknown Bridge Resource William N. Zanatta
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=1008211968.16830.1.camel@nc1701d \
--to=juergen.sawinski@mpimf-heidelberg.mpg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pozsy@sch.bme.hu \
/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.