Re: showing which hardware is unclaimed

view
thread

!MAILaRCHIVE_VOTE_RePLACE

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

To: Rick Jones <rick.jones2@...>

Cc: Matthew Wilcox <matthew@...>, Ingo Molnar <mingo@...>, Brandeburg, Jesse <jesse.brandeburg@...>, Kok, Auke-jan H <auke-jan.h.kok@...>, Linux Kernel Mailing List <linux-kernel@...>, NetDev <netdev@...>, e1000-list <e1000-devel@...>, linux-pci maillist <linux-pci@...>, Jeff Garzik <jeff@...>, Andrew Morton <akpm@...>, David S. Miller <davem@...>, Linus Torvalds <torvalds@...>, Ronciak, John <john.ronciak@...>, Allan, Bruce W <bruce.w.allan@...>, Greg KH <greg@...>, Arjan van de Ven <arjan@...>, Rafael J. Wysocki <rjw@...>

Subject: Re: showing which hardware is unclaimed

Date: Tuesday, April 8, 2008 - 4:35 pm

Hi!

quoted text> FWIW, this is what a command on "another OS" does with an unclaimed card:
> 
> # ioscan -fk -C lan
> Class     I  H/W Path  Driver  S/W State   H/W Type     Description
> ====================================================================
> lan       0  0/0/3/0   intl100   CLAIMED     INTERFACE    Intel PCI Pro 
> 10/100Tx Server Adapter
> lan       1  0/1/2/0   igelan    CLAIMED     INTERFACE    HP PCI 
> 1000Base-T Core
> lan       2  0/2/1/0   iether    CLAIMED     INTERFACE    HP A7012-60001 
> PCI/PCI-X 1000Base-T Dual-port Adapter
> lan       3  0/2/1/1   iether    CLAIMED     INTERFACE    HP A7012-60001 
> PCI/PCI-X 1000Base-T Dual-port Adapter
> lan       4  0/3/1/0   ixgbe     UNCLAIMED   UNKNOWN      PCI-X Ethernet 
> (17d55831)
> 
> I'd probably call that "unclaimed" rather than "broken" but that may 
> just be a preference thing.

`lspci -k' already reports which devices are claimed by which driver.

				Have a nice fortnight
-- 
Martin `MJ' Mares                          <mj@ucw.cz>   http://mj.ucw.cz/
Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth
MS has designed a perfect copy protection scheme: There is no reason to pirate Vista.
--
unsubscribe noticeTo 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/

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:

[regression] e1000e broke e1000 (was: Re: [ANNOUNCE] e1000 t..., Ingo Molnar, (Tue Apr 8, 2:39 pm)

RE: [regression] e1000e broke e1000 (was: Re: [ANNOUNCE] e10..., Brandeburg, Jesse, (Tue Apr 8, 3:43 pm)

Re: [regression] e1000e broke e1000 (was: Re: [ANNOUNCE] e10..., Ingo Molnar, (Tue Apr 8, 3:59 pm)

Re: [regression] e1000e broke e1000 (was: Re: [ANNOUNCE] e10..., Matthew Wilcox, (Tue Apr 8, 4:04 pm)

Re: [regression] e1000e broke e1000 (was: Re: [ANNOUNCE] e10..., Ingo Molnar, (Tue Apr 8, 4:17 pm)

showing which hardware is unclaimed, Rick Jones, (Tue Apr 8, 4:13 pm)

Re: showing which hardware is unclaimed, Martin Mares, (Tue Apr 8, 4:35 pm)

Re: [regression] e1000e broke e1000, Dan Noe, (Tue Apr 8, 4:12 pm)

Re: [regression] e1000e broke e1000, Matthew Wilcox, (Tue Apr 8, 4:20 pm)

Re: [regression] e1000e broke e1000, Dan Noe, (Tue Apr 8, 4:39 pm)

Re: [regression] e1000e broke e1000, Ingo Molnar, (Tue Apr 8, 4:35 pm)

Re: [regression] e1000e broke e1000, Martin Mares, (Tue Apr 8, 4:36 pm)

Re: [regression] e1000e broke e1000 (was: Re: [ANNOUNCE] e10..., Matthew Wilcox, (Tue Apr 8, 3:32 pm)

Re: [regression] e1000e broke e1000 (was: Re: [ANNOUNCE] e10..., Ingo Molnar, (Tue Apr 8, 3:51 pm)

Re: [regression] e1000e broke e1000, Bill Davidsen, (Wed Apr 9, 8:52 pm)

Re: [regression] e1000e broke e1000, Ingo Molnar, (Fri Apr 11, 4:59 am)

Re: [regression] e1000e broke e1000, Jeff Garzik, (Tue Apr 8, 3:56 pm)

Re: [regression] e1000e broke e1000, Ingo Molnar, (Tue Apr 8, 4:06 pm)

Re: [regression] e1000e broke e1000, Kok, Auke, (Tue Apr 8, 4:31 pm)

Re: [regression] e1000e broke e1000, Ingo Molnar, (Wed Apr 9, 3:12 pm)

Re: [regression] e1000e broke e1000, Jeff Garzik, (Wed Apr 9, 3:33 pm)

Re: [regression] e1000e broke e1000, Ingo Molnar, (Fri Apr 11, 7:30 am)

Re: [regression] e1000e broke e1000, Chris Friesen, (Fri Apr 11, 11:40 am)

Re: [regression] e1000e broke e1000, Willy Tarreau, (Fri Apr 11, 3:29 pm)

Re: [regression] e1000e broke e1000, Jeff Garzik, (Tue Apr 8, 4:19 pm)

Re: [regression] e1000e broke e1000, Ingo Molnar, (Tue Apr 8, 4:33 pm)

Re: [regression] e1000e broke e1000, Jeff Garzik, (Tue Apr 8, 4:56 pm)

[patch] e1000=y && e1000e=m regression fix (was: Re:..., Ingo Molnar, (Wed Apr 9, 3:38 pm)

Re: [patch] e1000=y && e1000e=m regression fix (was:..., Frans Pop, (Wed Apr 9, 4:49 pm)

Re: [patch] e1000=y && e1000e=m regression fix (was:..., Krzysztof Halasa, (Wed Apr 9, 7:59 pm)

Re: [patch] e1000=y && e1000e=m regression fix (was:..., Linus Torvalds, (Wed Apr 9, 9:40 pm)

Re: [patch] e1000=y && e1000e=m regression fix (was:..., Krzysztof Halasa, (Thu Apr 10, 5:57 am)

Re: [patch] e1000=y && e1000e=m regression fix (was:..., Linus Torvalds, (Thu Apr 10, 10:30 am)

Re: [patch] e1000=y && e1000e=m regression fix (was:..., Krzysztof Halasa, (Thu Apr 10, 5:35 pm)

Re: [patch] e1000=y && e1000e=m regression fix (was:..., Grant Grundler, (Thu Apr 10, 1:55 pm)

Re: [patch] e1000=y && e1000e=m regression fix (was:..., Linus Torvalds, (Thu Apr 10, 3:27 pm)

Re: [patch] e1000=y && e1000e=m regression fix (was:..., Matthew Wilcox, (Thu Apr 10, 2:04 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Kok, Auke, (Thu Apr 10, 2:26 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Chris Friesen, (Thu Apr 10, 5:20 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Kok, Auke, (Wed Apr 9, 4:12 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Kok, Auke, (Thu Apr 10, 2:29 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Ingo Molnar, (Thu Apr 10, 3:27 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Kok, Auke, (Thu Apr 10, 5:23 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Ingo Molnar, (Fri Apr 11, 7:26 am)

Re: [patch] e1000=y && e1000e=m regression fix, Christoph Hellwig, (Fri Apr 11, 7:36 am)

Re: [patch] e1000=y && e1000e=m regression fix, Ingo Molnar, (Fri Apr 11, 8:16 am)

Re: [patch] e1000=y && e1000e=m regression fix, Kok, Auke, (Fri Apr 11, 12:22 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Martin Mares, (Fri Apr 11, 1:10 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Christoph Hellwig, (Fri Apr 11, 12:45 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Linus Torvalds, (Fri Apr 11, 1:34 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Daniel Barkalow, (Fri Apr 11, 6:06 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Linus Torvalds, (Fri Apr 11, 7:00 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Jeff Garzik, (Fri Apr 11, 7:43 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Linus Torvalds, (Sun Apr 13, 5:13 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Ingo Molnar, (Mon Jun 9, 3:24 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Ondrej Zary, (Sun Apr 13, 5:34 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Christoph Hellwig, (Sat Apr 12, 9:07 am)

Re: [patch] e1000=y && e1000e=m regression fix, , (Fri Apr 11, 7:58 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Daniel Barkalow, (Fri Apr 11, 7:15 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Jeff Garzik, (Fri Apr 11, 6:21 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Daniel Barkalow, (Fri Apr 11, 7:05 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Matthew Wilcox, (Fri Apr 11, 1:53 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Linus Torvalds, (Fri Apr 11, 2:51 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Dan Noe, (Fri Apr 11, 5:01 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Krzysztof Halasa, (Fri Apr 11, 4:22 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Linus Torvalds, (Fri Apr 11, 4:29 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Matthew Wilcox, (Fri Apr 11, 3:01 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Linus Torvalds, (Fri Apr 11, 4:21 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Willy Tarreau, (Fri Apr 11, 3:25 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Matthew Wilcox, (Fri Apr 11, 3:38 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Kok, Auke, (Fri Apr 11, 1:26 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Philip Craig, (Thu Apr 10, 8:46 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Randy Dunlap, (Thu Apr 10, 5:44 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Andi Kleen, (Fri Apr 11, 3:54 am)

Re: [patch] e1000=y && e1000e=m regression fix, Kok, Auke, (Thu Apr 10, 5:52 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Ingo Molnar, (Wed Apr 9, 4:53 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Jeff Garzik, (Wed Apr 9, 3:50 pm)

Re: [patch] e1000=y && e1000e=m regression fix, Ingo Molnar, (Wed Apr 9, 4:04 pm)

Re: [E1000-devel] [regression] e1000e broke e1000, Kok, Auke, (Tue Apr 8, 4:47 pm)

Navigation

Popular discussions


linux-kernel:
Greg Kroah-Hartman	[PATCH 004/196] Chinese: add translation of SubmittingPatches
david	Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
Linus Torvalds	Linux 2.6.21-rc6
holzheu	Re: [RFC/PATCH] Documentation of kernel messages
git:

openbsd-misc:

linux-netdev:
Eric Dumazet	Re: Multicast packet loss
jamal	Re: iproute2 action/policer question
Gerrit Renker	[PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side)
Jens Låås	Re: tx queue hashing hot-spots and poor performance (multiq, ixgbe)

Colocation donated by:

Online users

hemisama87q

Syndicate