Date: Thu, 02 Oct 2008 23:33:28 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: bagavathykumar.m@hcl.in Cc: freebsd-hackers@freebsd.org Subject: Re: i386/127710: My driver PCI probe is not called for my correspondingdevice ID and Vendor ID Message-ID: <20081002.233328.-432820840.imp@bsdimp.com> In-Reply-To: <68C9F31EF19DB6448F515EF294028FDEE99BCE@chn-hclt-evs05.HCLT.CORP.HCL.IN> References: <68C9F31EF19DB6448F515EF294028FDEE999AB@chn-hclt-evs05.HCLT.CORP.HCL.IN> <200810011127.14593.jhb@freebsd.org> <68C9F31EF19DB6448F515EF294028FDEE99BCE@chn-hclt-evs05.HCLT.CORP.HCL.IN>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <68C9F31EF19DB6448F515EF294028FDEE99BCE@chn-hclt-evs05.HCLT.CORP.HCL.IN>
"Bagavathy Kumar Mahendran " <bagavathykumar.m@hcl.in> writes:
:
: Dear Baldwin,
: Thanks for your support .but my pci probe function is not
: getting called for my device id and vendor id. Because pccbb driver
: already sets the device_set_desc as PCI-CardBus Bridge. So is there any
: other option for me to make my_pciprobe function to be called for my
: corresponding device id and vendor id.
That's not why your probe isn't called. Setting a description is
standard behavior for the probe routine. Are you sure that the device
probe routine is getting called at all for any device? Have you tried
just leaving cbb out of the kernel? I recently fixed the original
problem in cbb (the fact it doesn't check the bridge type too), maybe
you could try to pick up that fix as well?
Warner
: Thanks,
:
: Regards,
: Bagavathy kumar .M
:
:
:
: -----Original Message-----
: From: John Baldwin [mailto:jhb@freebsd.org]
: Sent: Wednesday, October 01, 2008 8:57 PM
: To: freebsd-hackers@freebsd.org
: Cc: Bagavathy Kumar Mahendran ; Warner Losh
: Subject: Re: FW: i386/127710: My driver PCI probe is not called for my
: correspondingdevice ID and Vendor ID
:
: On Wednesday 01 October 2008 08:50:15 am Bagavathy Kumar Mahendran
: wrote:
: >
: > Dear All,
: > Iam writing a new driver for a SAS/SATA Controller having
: a
: > Class ID -0x01
: > Sub Class - 0x07
: > Programming Interface - 0x00
: >
: > Hence instead of my probe function the Static build Card Bus Driver
: cbb
: > is attaching just by simply checking sub class 0x07 and programming
: > interface 0x00.hence my probe gets failed. Kindly help me in resolving
: > this .what I thought is to add the card bus driver a checking of CLASS
: > ID in its pci probe function.
:
: The pccbb driver returns BUS_PROBE_DEFAULT (it should probably return
: GENERIC
: in the case where it matches only on class codes). Your driver just
: needs to
: return a numerically higher value (but still < 0) to claim the device.
: You
: can probably use BUS_PROBE_VENDOR or BUS_PROBE_DEFAULT + 1.
:
: --
: John Baldwin
:
: DISCLAIMER:
: -----------------------------------------------------------------------------------------------------------------------
:
: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
: It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in
: this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates.
: Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of
: this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have
: received this email in error please delete it and notify the sender immediately. Before opening any mail and
: attachments please check them for viruses and defect.
:
: -----------------------------------------------------------------------------------------------------------------------
:
:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081002.233328.-432820840.imp>