Sorry, many engineers are so used to internal people getting bug updates with
visible e-mail addresses and the ability to update bugster directly that they
don't realize external users have neither and get e-mails they can't respond
to, with no clue who to contact to provide more information.

I've cc'ed the responsible engineer, Saurabh, on this e-mail, so you can
communicate further on this issue.

        -Alan Coopersmith-           alan.coopersmith at sun.com
         Sun Microsystems, Inc. - X Window System Engineering



Masayuki Murayama wrote:
> I'm sorry if it is not a right mailing list for the issue.
> 
> I'm the submitter of CR6890550 below. The responsible engineer of the cr
> commented that further tests would be required to add the new PCI device
> id to bfe driver. I'd like to do what are required, and to send the result,
> but there is no mail address to contact the engineer.
> 
>  Should I request for sponsor here, or is there another way?
> 
> My SCA is OS0107
> 
> regards,
> 
> Masayuki Murayama
> 
> ----- Original Message -----
>> Date: Mon, 12 Oct 2009 11:02:58 -0600 (MDT)
>> From: bugmail-sender at Sun.COM
>> Subject: CR 6890550 Updated, <User 1-5Q-6307> now responsible engineer, P3
>> driver/bfe bfe should support pci14e4,4401 device
>> To: undisclosed-recipients:;
>>
>>
>> *Synopsis*: bfe should support pci14e4,4401 device
>>
>> Due to a change requested by <User 1-5Q-6307>,
>> <User 1-5Q-6307> is now the responsible engineer for:
>>
>> CR 6890550 changed on Oct 12 2009 by <User 1-5Q-6307>
>>
>> === Field ============ === New Value ============= === Old Value ============
> =
>> Description            New Note                                              
>  
>> Responsible Engineer   <User 1-5Q-6307>                                      
>  
>> Status                 3-Accepted                  1-Dispatched              
>  
>> ====================== =========================== ==========================
> =
>>     
>> *Change Request ID*: 6890550
>>
>> *Synopsis*: bfe should support pci14e4,4401 device
>>
>>  Product: solaris
>>  Category: driver
>>  Subcategory: bfe
>>  Type: Defect
>>  Subtype: 
>>  Status: 3-Accepted
>>  Substatus: 
>>  Priority: 3-Medium
>>  Introduced In Release: 
>>  Introduced In Build: 
>>  Responsible Engineer: <User 1-5Q-6307>
>>  Keywords: opensolaris
>>
>> === *Description* ===========================================================
> =
>> Category
>>   solaris/driver (Hardware Support - Devices/Drivers)
>> Sub-Category
>>   bfe
>> Description
>>   As bfe driver for broadcom bcm4401 fast ethernet nic in snv124
>> supports only pci14e4,970c device, my bcm4401 based pci add-on card, which pc
> i vendor/device id is pci14e4,4401, is not detected right after snv124
>> installation.
>> pci14e4,4402 and pci14e4,170c are also known as ids for the bcm4401 nic.
>> So bfe should support these three devices too, I think
>> Frequency
>>   Always
>> Regression
>>   No
>> Steps to Reproduce
>>   Just install snv124, then see /etc/driver_aliases.
>> So, following command failed.
>> ifconfig bfe0 plumb
>> Expected Result
>>   The lines below should be also included in /etc/driver_aliases right after
>> opensolaris installation.
>>  bfe "pci14e4,4401"
>>  bfe "pci14e4,4402"
>>  bfe "pci14e4,170c"
>> Actual Result
>>   installing snv124, there is an entry for bfe below in /etc/driver_aliases
>> bfe "pci14e4,970c"
>> Error Message(s)
>>   N/A
>> Test Case
>>   N/A
>> Workaround
>>   do following for my nic card
>> update_drv -a -i "pci14e4,4401" bfe
>> Additional configuration information
>>   the node information in the output of prtconf -v for my bcm4401 based pci
>> add-on card:
>>            Node 0x00001d
>>                assigned-addresses:  82040810.00000000.febfc000.00000000.0000
> 2000
>>                reg:  00040800.00000000.00000000.00000000.00000000.02040810.0
> 0000000.00000000.00000000.00002000
>>                compatible: 'pci14e4,4401.14e4.8401.1' + 'pci14e4,4401.14e4.8
> 401' + 'pci14e4,8401' + 'pci14e4,4401.1' + 'pci14e4,4401' + 'pciclass,020000' 
> + 'pciclass,0200'
>>                model:  'Ethernet controller'
>>                power-consumption:  00000001.00000001
>>                devsel-speed:  00000000
>>                interrupts:  00000001
>>                max-latency:  00000000
>>                min-grant:  00000000
>>                subsystem-vendor-id:  000014e4
>>                subsystem-id:  00008401
>>                unit-address:  '1'
>>                class-code:  00020000
>>                revision-id:  00000001
>>                vendor-id:  000014e4
>>                device-id:  00004401
>>                name:  'pci14e4,8401'
>>
>> *** (#1 of 2): 2009-10-12 13:58:28 GMT+00:00 <User 1-F4SZV>
>>
>> I didn't have access to the hardware and that's the reason I didn't add those
>  PCI-ID. If you access to the hardware, can you do basic testing and let me kn
> ow the result?
>> *** (#2 of 2): 2009-10-12 16:54:05 GMT+00:00 <User 1-5Q-6307>
>>
>>
>> === *Public Comments* =======================================================
> =
>> === *Workaround* ============================================================
> =
>> === *Additional Details* ====================================================
> =
>>        Targeted Release: 
>>        Commit To Fix In Build: 
>>        Fixed In Build: 
>>        Integrated In Build: 
>>        Verified In Build: 
>>  See Also: 6882713, 6890551
>>  Duplicate of: 
>>  Hooks:
>>        Hook1: 
>>        Hook2: 
>>        Hook3: 
>>        Hook4: 
>>        Hook5: 
>>        Hook6: <email address omitted>
>>  Program Management: 
>>  Root Cause: 
>>  Fix Affects Documentation: No
>>  Fix Affects Localization: No
>>
>> === *History* ===============================================================
> =
>>        Date Submitted: 2009-10-12 13:58:27 GMT+00:00
>>        Submitted By: <User 1-F4SZV>
>>
>>        Status Changed    Date Updated                  Updated By
>>        3-Accepted        2009-10-12 16:54:25 GMT+00:00 <User 1-5Q-6307>
>>
>>
>> === *Service Request* =======================================================
> =
>>        Impact: Limited
>>        Functionality: Secondary
>>        Severity: 4
>>        Product Name: solaris
>>        Product Release: solaris_nevada
>>        Product Build: snv_124
>>        Operating System: solaris_nevada
>>        Hardware: x86
>>        Submitted Date: 2009-10-12 13:58:28 GMT+00:00
>>
>>
>> === *Service Request* =======================================================
> =
>>        Impact: Limited
>>        Functionality: Secondary
>>        Severity: 4
>>        Product Name: solaris
>>        Product Release: solaris_nevada
>>        Product Build: snv_124
>>        Operating System: solaris_nevada
>>        Hardware: x86
>>        Submitted Date: 2009-10-12 13:58:48 GMT+00:00
>>
>>
>> === *Multiple Release (MR) Cluster* - 0 =====================================
> =
> 
> _______________________________________________
> request-sponsor mailing list
> request-sponsor at opensolaris.org

Reply via email to