| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
- Const'ify and static'ize as appropriate.
- Use __FBSDID().
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
| |
Requested by: jhb
|
|
|
|
|
|
|
| |
and processing IPSec traffic.
Approved by: gnn (mentor)
MFC after: 1 week
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
| |
Also report current link state while auto-negotiation is in
progress.
With this change link loss should be reported within a second
and drivers that rely on link state should work.
Reported by: Pete French < petefrench at ticketswitch dot com >
Tested by: Pete French < petefrench at ticketswitch dot com >
MFC after: 1 week
|
| |
|
| |
|
|
|
|
|
|
|
| |
implementation.
Obtained from: Chelsio Inc.
MFC after: 1 week
|
|
|
|
|
| |
Obtained from: Chelsio Inc.
MFC after: 3 days
|
|
|
|
|
|
|
| |
stmxcsr, clflush, lfence, mfence, sfence, syscall, sysret, sysenter,
sysexit, pause, monitor, mwait, and swapgs (amd64 only).
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
It is possible that the audit pipe(s) have different preselection configs
then the global preselection mask.
Spotted by: Vincenzo Iozzo
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
- Extend the DS1339 driver to recognize more chips in the family:
DS1337, DS1338, DS1339 are now supported
- Provide run-time chip detection
Reviewed, tested by: stas
Obtained from: Piotr Ziecik kosmo ! semihalf dot com
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
(glxsb_process()) we don't block others when looking for our session.
- Simplify the loop responsible for freeing sessions on detach.
- No need to drop a lock around malloc(M_NOWAIT).
- Treat ses_used as boolean.
- Avoid gotos where possible.
- Various style(9) fixes.
Reviewed by: philip, Patrick Lamaiziere <patfbsd@davenulle.org>
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This driver supports GW3887 based chipsets and works on
x86/powerpc/sparc64. You need upgtfw kernel module before loading
upgt(4). Please see the manpage.
Obtained from: OpenBSD
|
|
|
|
| |
manipulate the verbose description of a device.
|
|
|
|
|
|
| |
pci_get_vendor() and pci_get_device() don't do configuration space
accessses so cahcing them makes no sense.
Pointed out by: jhb, imp, des
|
| |
|
|
|
|
|
|
|
| |
Move the NULL pointer check to the vfs_deleteopt() function.
Discussed with: rodrigc
MFC after: 3 days
|
| |
|
|
|
|
| |
the child is out of reset... <blush>
|
| |
|
|
|
|
|
|
| |
Reviewed by: sam
Approved by: sam
MFC after: 3 days
|
| |
|
|
|
|
| |
- Update copyright years.
|
| |
|
| |
|
|
|
|
| |
Bug tracked down by: Patrick Lamaiziere <patfbsd@davenulle.org>
|
|
|
|
|
|
| |
when looking for them.
Idea from: Patrick Lamaiziere <patfbsd@davenulle.org>
|
|
|
|
| |
Submitted by: N.J. Mann
|
|
|
|
|
|
|
| |
on a variety of cards. Adjust the comments accordingly to match the
code. Even if the vendor chose 0xffff for the device ID, the vendor
ID can't be 0xffff, so the test is still valid from a standards
perspective.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
found in Soekris hardware, for instance). The hardware supports acceleration
of AES-128-CBC accessible through crypto(4) and supplies entropy to random(4).
TODO:
o Implement rndtest(4) support
o Performance enhancements
Submitted by: Patrick Lamaizière <patfbsd -at- davenulle.org>
Reviewed by: jhb, sam
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
There is no reason the fdopen() routine needs Giant. It only sets
curthread->td_dupfd, based on the device unit number of the cdev.
I guess we won't get massive performance improvements here, but still, I
assume we eventually want to get rid of Giant.
|
| |
|
|
|
|
|
|
|
| |
completely dynamic sbuf.
Obtained from: Varnish
MFC after: 2 weeks
|
|
|
|
| |
and style(9) cleanup.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that I have. Wait up to 1.1s for the card to become ready. Document
what the standards say, and use that to justify the behavior in the
code: PCI standard says that a card must respond to configuration
cycles within 2^25 cycles after reset goes high, which is
approximately 1s. Therefore, give cards a little break and wait for
up to 1.1s for VENDOR to become valid. Only look at the vendor part
of the ID, since only it can't be 0xffff (although in practice
vendor/device will always be != 0xfffffffff). Include detailed
pointers to standards so epople understand why we're doing what we're
doing and why it just might be OK. Make it clear in the timeout
message that it is just a warning, sinc we try to soldier on as best
we can anyway.
This should eliminate an error message that r181453 produced on
certain Atheros cards.
|
|
|
|
|
|
|
|
|
|
|
|
| |
more mappings to the same physical page have different memory types, i.e.,
PAT settings. Consequently, if pmap_change_attr() is applied to a virtual
address range within the kernel map, then the corresponding ranges of the
direct map also need to be changed. Enhance pmap_change_attr() to handle
this case automatically.
Add a comment describing what pmap_change_attr() does.
Discussed with: jhb
|
|
|
|
|
|
|
| |
driver's set of valid flags. Otherwise, wpa_supplicant wouldn't
report an error for old wi cards that can't do WPA.
Reviewed by: sam@
|
|
|
|
|
|
|
|
|
|
|
|
| |
and also holds things up, check every 20ms to see if we can read the
vendor of device 0.0. It will be 0xffffffff until the card is out of
reset. Always wait at least 20ms, for safety.
I think this is a better fix to the reset problem. However, I did it
as a separate commit in case something bad happens, people can roll
back to the commit before this one to see if that gives them reliable
behavior. I don't have FreeBSD up on enough machines to do exhaustive
testing on all known bridges...
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
some bridge + card combinations that take longer for reasons unknown.
Adjust the timeout to be 100ms on all !RICOH bridges, but leave RICOH
at 400ms. The 400ms is "lore" from other open source projects, and
I've never see my ricoh bridge chips take this long. Maybe it is the
same thing? Maybe a bit should be read instead of a hard-wired pause?
After this adjustment, a few cards that I'd insert and get only:
cbb0: card_power: 3V
cbb0: card_power: 0V
with full debugging enabled would actually try to attach.
Reported by: sam@ (I think)
MFC after: 3 days
|
| |
|
|
|
|
| |
Approved by: kib
|
|
|
|
|
|
|
|
|
| |
set the %eflags used during a BIOS call via BTX to 0x202. Previously
the flags field was uninitialized garbage, and thus it was "random" if
interrupts were enabled or not during BIOS calls.
- Use constants from <machine/psl.h> for fields in %eflags.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- I had errantly assumed that all user requests should run with interrupts
enabled. User requests for software interrupts, however, need to disable
interrupts (and tracing) just like hardware interrupts.
- Disable alignment checking when emulating a hardware interrupt as well
(based on the description of the real mode operation of the 'INT'
instruction in the IA-32 manuals).
- Use constants for fields in %eflags.
Tested by: bz
MFC after: 3 days
|