Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.os.development > #9779
| From | "wolfgang kern" <nowhere@never.at> |
|---|---|
| Newsgroups | alt.os.development |
| Subject | Re: PCI-enum and SouthBridge behaviour... |
| Date | 2016-07-26 12:48 +0200 |
| Organization | KESYS-development |
| Message-ID | <nn7gfg$1scg$1@gioia.aioe.org> (permalink) |
| References | (1 earlier) <nn2o8h$v9j$1@dont-email.me> <nn2vmj$1mhk$1@gioia.aioe.org> <nn4ab2$ct2$1@dont-email.me> <nn4knt$1n5v$1@gioia.aioe.org> <20160725215519.0a36a777@_> |
Rod Pemberton wrote: >> No, only a few mS if I just scan until all desired are found, but a >> full scan over all possible 256 busses would take seconds. > Can you do a full scan when you install your OS and save the output? I do a full scan for testing new hardware only. The OS-installer just checks if the machine is KESYS-compliant and it wont install on unknown hardware anyway. > Then, do a short scan each boot to detect for changes to the known > AMD/ATI stuff with documentation? Yeah, after installed the boot will just check if anything changed. > You're not going to be supporting that fuller set. So why check for > it multiple times? For now I do it a second time when missing PCI-devices which I know to have inside after reactivate them. I still check if any preceding action can make my first PCI-scan show me all present devices. __ wolfgang
Back to alt.os.development | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
PCI-enum and SouthBridge behaviour... "wolfgang kern" <nowhere@never.at> - 2016-07-22 21:53 +0200
Re: PCI-enum and SouthBridge behaviour... James Harris <james.harris.1@gmail.com> - 2016-07-24 16:52 +0100
Re: PCI-enum and SouthBridge behaviour... "wolfgang kern" <nowhere@never.at> - 2016-07-24 19:54 +0200
Re: PCI-enum and SouthBridge behaviour... James Harris <james.harris.1@gmail.com> - 2016-07-25 07:07 +0100
Re: PCI-enum and SouthBridge behaviour... "wolfgang kern" <nowhere@never.at> - 2016-07-25 11:04 +0200
Re: PCI-enum and SouthBridge behaviour... James Harris <james.harris.1@gmail.com> - 2016-07-25 10:30 +0100
Re: PCI-enum and SouthBridge behaviour... "wolfgang kern" <nowhere@never.at> - 2016-07-25 14:06 +0200
Re: PCI-enum and SouthBridge behaviour... James Harris <james.harris.1@gmail.com> - 2016-07-25 13:16 +0100
Re: PCI-enum and SouthBridge behaviour... "wolfgang kern" <nowhere@never.at> - 2016-07-26 13:09 +0200
Re: PCI-enum and SouthBridge behaviour... James Harris <james.harris.1@gmail.com> - 2016-07-26 15:14 +0100
Re: PCI-enum and SouthBridge behaviour... Rod Pemberton <NoHaveNotOne@bcczxcfrze.cam> - 2016-07-25 21:55 -0400
Re: PCI-enum and SouthBridge behaviour... "wolfgang kern" <nowhere@never.at> - 2016-07-26 12:48 +0200
Re: PCI-enum and SouthBridge behaviour... Rod Pemberton <NoHaveNotOne@bcczxcfrze.cam> - 2016-07-26 08:18 -0400
Re: PCI-enum and SouthBridge behaviour... "wolfgang kern" <nowhere@never.at> - 2016-07-26 20:11 +0200
Re: PCI-enum and SouthBridge behaviour... "wolfgang kern" <nowhere@never.at> - 2016-07-28 18:53 +0200
Re: PCI-enum and SouthBridge behaviour... "wolfgang kern" <nowhere@never.at> - 2016-07-29 19:47 +0200
Re: PCI-enum and SouthBridge behaviour... Rod Pemberton <NoHaveNotOne@zxdehrnyya.cam> - 2016-07-29 17:44 -0400
Re: PCI-enum and SouthBridge behaviour... "wolfgang kern" <nowhere@never.at> - 2016-07-30 09:44 +0200
Re: PCI-enum and SouthBridge behaviour... James Harris <james.harris.1@gmail.com> - 2016-07-30 12:55 +0100
Re: PCI-enum and SouthBridge behaviour... "wolfgang kern" <nowhere@never.at> - 2016-07-30 19:40 +0200
Re: PCI-enum and SouthBridge behaviour... James Harris <james.harris.1@gmail.com> - 2016-07-30 19:08 +0100
csiph-web