Re: pmq imports - problems
From: Slobodan Brcin \(eMVP\) (sbrcin_at_ptt.yu)
Date: 08/16/04
- Next message: Sorin C.: "Re: MAC ADDRESS being reported at 0000000"
- Previous message: Ann Adamson: "Re: pmq imports - problems"
- In reply to: Ann Adamson: "Re: pmq imports - problems"
- Next in thread: KM: "Re: pmq imports - problems"
- Reply: KM: "Re: pmq imports - problems"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 16 Aug 2004 19:34:59 +0200
Hi Ann,
Do not import inf files to component, just make component that will include them.
I don't how to say this better. You should add all files manually and not by using import option with inf file.
You will not have collision with MS components if MS decide to make their components for these chipsets this is due to fact that
your component only replace manual file copy that could be done after the image build from TD.
Best regards,
Slobodan
"Ann Adamson" <ann_adamson@hotmail.com> wrote in message news:4120e8fe$1@rpc1284.daytonoh.ncr.com...
> We have done some of this, but were hesitant to import all the INFs because
> we figure these will "appear" in a future release of the Component Database
> from Microsoft, and then we may end up with "versioning" issues. We were
> trying to only componentize the drivers that we needed to to make the thing
> boot, and to use the more generic components whenever possible.
>
> Ann
>
> "Slobodan Brcin (eMVP)" <sbrcin@ptt.yu> wrote in message
> news:Oz1S6v$eEHA.2044@TK2MSFTNGP10.phx.gbl...
> > Hi Ann,
> >
> > Actually manually componentizing Intel platforms is very easy from CD.
> > You create component that will contain all Intel inf files that you are
> interested in. (Less than MB can cover all chipsets Intel
> > ever made).
> >
> > Consider the fast that Intel rely on MS driver binaries and that they
> almost always provide just fancy text strings. (Gart
> > agp440.sys excluded since MS did not make inf file that cover third
> driver.)
> > Also by matching Compatible IDs you can find always original MS
> components.
> >
> > For instance of your first driver:
> > XPe component "PCI standard PCI-to-PCI bridge" uses PCI\CC_0604 as PnPID
> which matches ID from your list <DEVICEID
> > Order="5">PCI\CC_0604</DEVICEID>
> >
> > So having this component in your image and including appropriate inf file
> that contain string "DEV_0320" will solve all your
> > problems. BTW I can't find inf file with this ID (Probably some new piece
> of hardware)
> >
> > So this approach you can use with all hardware components, or you can use
> all standard components from minlogon MACRO, and just push
> > all inf files as well, that should cover all your chipsets except GART.
> >
> >
> > >So, it seems this idea of a "Platform Macro Component" built with
> Component
> > > Designer is pretty shaky right now. You have to do a lot of manual
> fiddling
> > > to get it right.
> >
> > It is up to you :(
> >
> > Best regards,
> > Slobodan
> >
> > "Ann Adamson" <ann_adamson@hotmail.com> wrote in message
> news:4113ed80$1@rpc1284.daytonoh.ncr.com...
> > > In all the documentation and sessions I've ever read/seen, they always
> talk
> > > about being able to use a .pmq file to produce a platform "Macro"
> component
> > > which pulls in all the necessary hw components to support your device.
> This
> > > seems like a GREAT idea, BUT...
> > >
> > > When I import .pmq files into Target Designer and Component Designer, I
> > > OFTEN get different results! It seems like the "matching" algorithms
> must
> > > be different. Does Component Designer just ignore the COMPATIBLEIDS
> > > section? That's what it looks like to me. Isn't this a bug?
> > >
> > > For example, from the section that follows from my .pmq file, Target
> > > Desiger matched and brought in the component "PCI Standard PCI-to-PCI
> > > Bridge" (PnPID(819):"PCI\CC_0604"), however, Component Designer did not
> find
> > > a match and did not bring in any component.
> > >
> > > <DEVICE ConfigFlags="0">
> > > <DEVICEDESC>PCI standard PCI-to-PCI bridge</DEVICEDESC>
> > > <HARDWAREIDS>
> > > <DEVICEID
> > >
> Order="1">PCI\VEN_8086&DEV_0320&SUBSYS_00000000&REV_04</DEVICEID
> > > >
> > > <DEVICEID
> > > Order="2">PCI\VEN_8086&DEV_0320&SUBSYS_00000000</DEVICEID>
> > > <DEVICEID Order="3">PCI\VEN_8086&DEV_0320&REV_04</DEVICEID>
> > > <DEVICEID Order="4">PCI\VEN_8086&DEV_0320</DEVICEID>
> > > <DEVICEID
> Order="5">PCI\VEN_8086&DEV_0320&CC_060400</DEVICEID>
> > > <DEVICEID
> Order="6">PCI\VEN_8086&DEV_0320&CC_0604</DEVICEID>
> > > </HARDWAREIDS>
> > > <COMPATIBLEIDS>
> > > <DEVICEID Order="1">PCI\VEN_8086&CC_060400</DEVICEID>
> > > <DEVICEID Order="2">PCI\VEN_8086&CC_0604</DEVICEID>
> > > <DEVICEID Order="3">PCI\VEN_8086</DEVICEID>
> > > <DEVICEID Order="4">PCI\CC_060400</DEVICEID>
> > > <DEVICEID Order="5">PCI\CC_0604</DEVICEID>
> > > </COMPATIBLEIDS>
> > > </DEVICE>
> > >
> > > In other cases, if there is a specific Intel Driver that has not yet
> been
> > > componentized, but a "standard" component will do, Target Designer can
> make
> > > a match, but Component Designer does not. In the following example, TD
> > > brought in the component "Standard Universal PCI to USB Host Controller"
> > > (PnPID(819):"PCI\CC_0C0300") but CD made no match. PLUS CD does not
> give
> > > errors when it cannot find a match!!
> > >
> > > <DEVICE ConfigFlags="0">
> > > <DEVICEDESC>Intel(R) 82801EB USB Universal Host Controller -
> > > 24D2</DEVICEDESC>
> > > <HARDWAREIDS>
> > > <DEVICEID
> > >
> Order="1">PCI\VEN_8086&DEV_24D2&SUBSYS_10798086&REV_02</DEVICEID
> > > >
> > > <DEVICEID
> > > Order="2">PCI\VEN_8086&DEV_24D2&SUBSYS_10798086</DEVICEID>
> > > <DEVICEID
> Order="3">PCI\VEN_8086&DEV_24D2&CC_0C0300</DEVICEID>
> > > <DEVICEID
> Order="4">PCI\VEN_8086&DEV_24D2&CC_0C03</DEVICEID>
> > > </HARDWAREIDS>
> > > <COMPATIBLEIDS>
> > > <DEVICEID Order="1">PCI\VEN_8086&DEV_24D2&REV_02</DEVICEID>
> > > <DEVICEID Order="2">PCI\VEN_8086&DEV_24D2</DEVICEID>
> > > <DEVICEID Order="3">PCI\VEN_8086&CC_0C0300</DEVICEID>
> > > <DEVICEID Order="4">PCI\VEN_8086&CC_0C03</DEVICEID>
> > > <DEVICEID Order="5">PCI\VEN_8086</DEVICEID>
> > > <DEVICEID Order="6">PCI\CC_0C0300</DEVICEID>
> > > <DEVICEID Order="7">PCI\CC_0C03</DEVICEID>
> > > </COMPATIBLEIDS>
> > > </DEVICE>
> > >
> > > So, it seems this idea of a "Platform Macro Component" built with
> Component
> > > Designer is pretty shaky right now. You have to do a lot of manual
> fiddling
> > > to get it right.
> > >
> > > Ann
> > >
> > >
> >
> >
>
>
- Next message: Sorin C.: "Re: MAC ADDRESS being reported at 0000000"
- Previous message: Ann Adamson: "Re: pmq imports - problems"
- In reply to: Ann Adamson: "Re: pmq imports - problems"
- Next in thread: KM: "Re: pmq imports - problems"
- Reply: KM: "Re: pmq imports - problems"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
