FW: i386/127710: My driver PCI probe is not called for mycorrespondingdevice ID and Vendor ID - FreeBSD
This is a discussion on FW: i386/127710: My driver PCI probe is not called for mycorrespondingdevice ID and Vendor ID - FreeBSD ; 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 ...
-
FW: i386/127710: My driver PCI probe is not called for mycorrespondingdevice ID and Vendor ID
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.
Thanks
With Regards,
Bagavathy kumar .M
-----Original Message-----
From: Remko Lodder [mailto:remko@FreeBSD.org]
Sent: Wednesday, October 01, 2008 5:48 PM
To: Bagavathy Kumar Mahendran
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: i386/127710: My driver PCI probe is not called for my
correspondingdevice ID and Vendor ID
Bagavathy kumar . M wrote:
Please submit this question to the hackers@FreeBSD.org mailinglist.This
is not a PR (yet), you might have done something wrong to your code or
are missing logic(s) which are needed in that case.
I will close the ticket because of that. Thanks for taking the time to
report this and for using FreeBSD, it's appreciated!
--
/"\ Best regards, | remko@FreeBSD.org
\ / Remko Lodder | remko@EFnet
X http://www.evilcoder.org/ |
/ \ ASCII Ribbon Campaign | Against HTML Mail and News
DISCLAIMER:
-----------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential andintended for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or itsaffiliates. Any views or opinions presented in
this email are solely those of the author and may not necessarily reflectthe 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-mailis strictly prohibited. If you have
received this email in error please delete it and notify the senderimmediately. Before opening any mail and
attachments please check them for viruses and defect.
-----------------------------------------------------------------------------------------------------------------------
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/lis...reebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
-
RE: FW: i386/127710: My driver PCI probe is not called for mycorrespondingdevice ID and Vendor ID
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.
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 inresolving
> 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 andintended for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or itsaffiliates. Any views or opinions presented in
this email are solely those of the author and may not necessarily reflectthe 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-mailis strictly prohibited. If you have
received this email in error please delete it and notify the senderimmediately. Before opening any mail and
attachments please check them for viruses and defect.
-----------------------------------------------------------------------------------------------------------------------
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/lis...reebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"