Did you try bcme driver ?
http://www.bolthole.com/solaris/HCL/devices.php
Try adding the PCI ID to /etc/drivers_aliases (man add_drv). It may work.
This message posted from opensolaris.org
___
opensolaris-code mailing list
opensolaris-code@opensolar
I've been peeking around the forum looking for anything on the Broadcom
BCM5787M chipset & doesn't seem to be turning anything up...
Does anyone know if there are any hacks to get the GbE interfaces using this
chipset on my motherboard to work?
Thanks,
-Darby
This message posted from openso
In sys/mkdev.h, we have:
/*
* SVR3/Pre-EFT device number constants.
*/
#define ONBITSMAJOR 7 /* # of SVR3 major device bits */
#define ONBITSMINOR 8 /* # of SVR3 minor device bits */
#define OMAXMAJ 0x7f/* SVR3 max major value */
#define OMAXMIN 0xff/*
On Tue, May 27, 2008 at 11:12:10AM -0700, Garrett D'Amore wrote:
> A semi-concrete example is that the driver needs to register "mixers"
> with the mixer framework. It does this at attach time currently. What
> gets registered can be different depending upon these tunables -- such
> as whether
> So, there is no way to turn off the "storage key" before faulting in the
> page, and then turning it back on after the input has completed?
No.
The hardware has always worked this way - it's defined in its principle of
operations that I/O is part of the "change recording" mechanism. It is
imp
Right now, drivers using sys/ioccom.h definitions for _IOR, _IORW, etc.
are limited to passing structures that are at most 255 bytes. This
seems a bit limiting, at least to me. In particular, other operating
systems use a value that is much higher -- say 8191 maximum bytes.
This actually impa
Liane Praza wrote:
> Mike's two design questions are key to attacking this problem. I'd stay
> away from constraining driver/kernel configuration to be read only by a
> userland application.
Mixed feelings.
At a purist level, you are of course right.
At a somewhat different level, if we can m
Sushant Nirwan wrote:
> Davi wrote:
>> ct_tmpl_create() is currently only used by device contracts.
>> See device_contract(4).
>
> Currently I’m working on solaris 5.11 release snv_47 and snv_54.
> I did not find any folder like /system/contract/device. So how to
active device contract in
Jordan Brown wrote:
> Garrett D'Amore wrote:
>>> Why isn't the right answer to run an application that reads config
>>> files (or reads SMF properties) and issues ioctls to get the data into
>>> the driver?
>> Well, we can do that, but the problem is making sure that the above
>> operation is do
Garrett D'Amore wrote:
> You also need to have values that are persistent -- i.e. the driver
> could detach (e.g. due to idleness), and when it gets reloaded later
> (perhaps because it was now being used) you want to use the same values
> it had before. This means that you really need a pull r
Jordan Brown wrote:
> Garrett D'Amore wrote:
>
>>> Probably better is to key the configuration off of the /dev name,
>>> which hides that lower-level stuff.
>>>
>> Well, I'd settle for driver name and instance number. This is probably,
>> in some respects, simpler than /dev names, whic
Garrett D'Amore wrote:
>> Probably better is to key the configuration off of the /dev name,
>> which hides that lower-level stuff.
>
> Well, I'd settle for driver name and instance number. This is probably,
> in some respects, simpler than /dev names, which can vary for different
> kinds of de
Jordan Brown wrote:
> Garrett D'Amore wrote:
>> It *seem* to me, that a potentially superior way to handle this, at
>> least for my needs, is to figure out who to use SMF service
>> properties. The challenge becomes getting access to such properties
>> from the kernel, and notification in the k
Hi Neale,
Neale Ferguson wrote:
>> How quickly do you want an answer to this ?
>>
> Last week! ;-)
>
> It's not a write fault that's the problem here. It's when a read is done the
> page is marked dirty and fsflush will attempt to write it back out. Actually
> it's any read of the page (whe
Garrett D'Amore wrote:
> It *seem* to me, that a potentially superior way to handle this, at
> least for my needs, is to figure out who to use SMF service properties.
> The challenge becomes getting access to such properties from the kernel,
> and notification in the kernel when certain propert
> How quickly do you want an answer to this ?
Last week! ;-)
It's not a write fault that's the problem here. It's when a read is done the
page is marked dirty and fsflush will attempt to write it back out. Actually
it's any read of the page (whether caused by a read fault or a write fault).
Th
16 matches
Mail list logo
