> Please test the following diff if you have a system utilizing the
> BCM5709S chipset. This diff adds support for the fiber PHY coupled
> with the BCM5709S controller.
This is wrong. Test if you have *any* bnx. When a diff of this nasty
complexity and size goes by, noone could give a rats ass i
Why?
RAID mode is NOT a valid ID for ahci.
On Tue, Apr 06, 2010 at 09:09:47PM -0400, Brad wrote:
> On Mon, Mar 15, 2010 at 10:19:18PM -0400, Brad wrote:
> > The following diff adds the remaining PCI ids for the Intel AHCI
> > controllers with a RAID mode to the existing ICH8 / ICH10 PCI ids.
> >
Please test the following diff if you have a system utilizing the
BCM5709S chipset. This diff adds support for the fiber PHY coupled
with the BCM5709S controller.
Index: pci/if_bnx.c
===
RCS file: /cvs/src/sys/dev/pci/if_bnx.c,v
retr
On Sun, Nov 01, 2009 at 12:22:58AM -0400, Brad wrote:
> The following diff makes the ahci(4) driver use the same quirk
> across both the controller coming up in IDE mode as well as in
> native AHCI modes.
Still outstanding.
--
This message has been scanned for viruses and
dangerous content by Ma
On Mon, Mar 15, 2010 at 10:19:18PM -0400, Brad wrote:
> The following diff adds the remaining PCI ids for the Intel AHCI
> controllers with a RAID mode to the existing ICH8 / ICH10 PCI ids.
>
>
> Add the Intel ICH7 (82801GHM / GR), ICH9 (82801I) and ICH10 (82801JD),
> 6321ESB and PCH (3400) RAID
hopefully this is the last round;
- don't duplicate documentation from .h in .c
- move .h documentation to the same line as the #define for easier grepping
- reword .h doc slightly, mostly to fit on 1 line where possible, change
text for UQ_EHCI_NEEDTO_DISOWN to something that seems easier-reading
Hello,
On Tue, Apr 06, 2010 at 02:34:03PM -0600, Theo de Raadt wrote:
> > On Tue, Apr 06, 2010 at 11:55:21AM -0400, Ted Unangst wrote:
> > I'm sorry, but this is terrible. (Not your effort, which is
> > appreciated, but the whole function.) I do not like the idea of
> > adding a "be extra carefu
> If I continue to have say in this, wordexp() will never be in
> OpenBSD's libc. Perhaps if there is one open source project which
> refuses to have it, coders will continue avoiding use of wordexp().
Other than we know by the example of strlc* that doesnt' work ;)
Even though there are real re
> On Tue, Apr 6, 2010 at 1:53 AM, Matthew Haub
> wrote:
> > This patch adds support for wordexp(3) and wordfree(3) to libc. These
> > functions conform to IEEE Std 1003.1-2001 (POSIX). The implementation
> > comes from NetBSD and uses a shell builtin, "wordexp", to perform the
> > expansion in lin
People with AR9285/AR9287/AR9227 devices, please test the
following diff to see if there is no regression.
It adds support for newer AR9285 devices (XE) but it also
changes behavior for legacy AR9285 devices.
Damien
Index: athn.c
===
Whoops, reading too slow.
On Tue, Apr 06, 2010 at 05:41:59PM +0100, Nicholas Marriott wrote:
> Hi
>
> You'll have to implement wordexp(3) in libc too before this does us any
> good.
>
>
> On Tue, Apr 06, 2010 at 03:49:58PM +0930, Matthew Haub wrote:
> > Hello,
> >
> > On Fri, Apr 02, 2010 at
Hi
You'll have to implement wordexp(3) in libc too before this does us any
good.
On Tue, Apr 06, 2010 at 03:49:58PM +0930, Matthew Haub wrote:
> Hello,
>
> On Fri, Apr 02, 2010 at 07:08:43PM -0700, Philip Guenther wrote:
> > are we still tracking the upstream less(1) and if so, is the
> > behav
I think we should stand up to crap and not ever impliment it.
> On Tue, Apr 6, 2010 at 1:53 AM, Matthew Haub
> wrote:
> > This patch adds support for wordexp(3) and wordfree(3) to libc. These
> > functions conform to IEEE Std 1003.1-2001 (POSIX). The implementation
> > comes from NetBSD and uses
On Tue, Apr 6, 2010 at 1:53 AM, Matthew Haub
wrote:
> This patch adds support for wordexp(3) and wordfree(3) to libc. These
> functions conform to IEEE Std 1003.1-2001 (POSIX). The implementation
> comes from NetBSD and uses a shell builtin, "wordexp", to perform the
> expansion in line with the m
Hello,
The openssl command line tool treats the non-null terminated buffer
"mbuf" as a C string when using the pop3 s_client feature. This causes
a segmentation fault with malloc.conf option "J" set when BIO_printf()
runs off the end of the buffer. The following patch fixes PR 6282.
Matthew
Inde
On Mon, Apr 5, 2010 at 11:38 AM, Sean Kennedy
wrote:
> I concur, it was a Valid question on running OpenBSD in a VM.
really, i was very radical in the last email. really. shut it up and
hack. maybe starting helping the virtualbox guys to close the related
bug at http://www.virtualbox.org/ticket
On 2010/04/06 10:47, Stuart Henderson wrote:
> this brings the UQ_BAD_HID entries together, lines up the
> columns a bit better, and adds a short description for some
> of the quirks.
>
> any comments? ok?
better with some spaces->tabs (prompted by mail from halex).
Index: usb_quirks.c
=
this brings the UQ_BAD_HID entries together, lines up the
columns a bit better, and adds a short description for some
of the quirks.
any comments? ok?
Index: usb_quirks.c
===
RCS file: /cvs/src/sys/dev/usb/usb_quirks.c,v
retrieving
18 matches
Mail list logo