# ifconfig wi0 hidessid
ifconfig: hidessid: bad value
# uname -rs
FreeBSD 5.3-RELEASE
#
Daniel O'Connor escreveu:
On Tue, 15 Feb 2005 12:02, Daniel Dias Gonçalves wrote:
I setup a FreeBSD 5.3 with Senao SL-2511CD Plus ext2 802.11b in mode
HOSTAP.
Using scaning software, i view the name of the
Luiz,
NetBSD 2.0 have mode HIDDEN SSID in ifconfig and wi(4) ?
Who is porting the NetBSD wi driver ? Has a page of the patch?
Has some HACK to wi driver on FreeBSD as that one that force TX RATE:
//
http://excamera.com/cgi-bin/blosxom.cgi
Sun, 16 May 2004
*wi hostap fix, kind of*
Hello,
Looking at the mbuf statistics available in FreeBSD 4 and FreeBSD 5 I
can see that the statistics available in FreeBSD 5 are, surprisingly,
much less comprehensive. Is there any other place where I can find out
how many mbuf requests have been done, how many of them have waited,
Joerg Schilling [EMAIL PROTECTED] wrote:
- The official cdrecord source includes working
DVD support since March 1988, there is no need
to add broken DVD code that even breaks the CD writing
part of cdrecord because it ignores the purpose
On Mon, 14 Feb 2005 08:04:50 -0500, David Schultz [EMAIL PROTECTED] wrote:
Right, databases, language runtimes, and the small set of other
applications for which it really matters usually have their own
special-purpose allocators. I was counting on that when I said
that replacing malloc() is
Daniel,
Sorry, i'm wrong about that.
The hidden ssid ready driver is in OpenBSD (see WI_RID_ENH_SECURITY in
if_wi_ieee.h).
The NetBSD porting is just an auto rate fix.
The ifconfig support is in 6-CURRENT (or in the patch for 5.X).
[]s
Luiz
On Tue, 15 Feb 2005, [ISO-8859-1] Daniel Dias Gonçalves
On Mon, Feb 14, 2005 at 10:24:50PM -0800, Ashwin Chandra wrote:
In trying to create a simple kernel thread that prints out all
the processes data and stack size, i still get a panic fault
(vm_fault on no entry) at the printf statement...ive narrowed
it down to the ru_idrss variable that is
On Tuesday 15 February 2005 12:38, Borja Marcos wrote:
Hello,
Looking at the mbuf statistics available in FreeBSD 4 and FreeBSD 5 I
can see that the statistics available in FreeBSD 5 are, surprisingly,
much less comprehensive. Is there any other place where I can find out
how
I use $vmstat -z | grep Mbuf. The netstat -m output is broken,
because
fixing this would impose an additional atomic operation on each
alloc/free
which is a real performance killer.
Humm. Will check the vm.zone sysctl, thanks :-)
I guess there's a lot of interesting info there, but some of
Hi Stephan,
I'm happy to say that it's working now :)
I grabbed a 5.3-STABLE snapshot to get the updated kgdb and completely
reinstalled my 5.3-RELEASE system. I compiled the kernel using your
options and it worked straight away.
I have no idea why it didn't work before. It must be some boot
On Tue, 2005-02-15 at 11:55, Gerald Heinig wrote:
Hi Stephan,
I'm happy to say that it's working now :)
I grabbed a 5.3-STABLE snapshot to get the updated kgdb and completely
reinstalled my 5.3-RELEASE system. I compiled the kernel using your
options and it worked straight away.
I have
I maintain drivers for a PCI card which presents itself as having
16MB of address space. Eg:
mx0: Myrinet PCIXE mem 0xf900-0xf9ff irq 20 at device 3.0 on pci1
However, most of that address space does not need to be mapped into
the host. Really, only a little over 2MB needs to be
I maintain drivers for a PCI card which presents itself as having
16MB of address space. Eg:
mx0: Myrinet PCIXE mem 0xf900-0xf9ff irq 20 at device 3.0 on pci1
However, most of that address space does not need to be mapped into
the host. Really, only a little over 2MB needs to be
Andrew Gallatin wrote:
I maintain drivers for a PCI card which presents itself as having
16MB of address space. Eg:
mx0: Myrinet PCIXE mem 0xf900-0xf9ff irq 20 at device 3.0 on pci1
However, most of that address space does not need to be mapped into
the host. Really, only a little over
Scott Long writes:
You can use pmap_mapdev() to create a KVA mapping of an arbitrary
physaddr+len. In fact, this is exactly what newbus uses to create the
PCI MEMIO resources when bus_alloc_resource() is called. I'm not sure
if the range is mapped and activated before the driver
From: Scott Long [EMAIL PROTECTED]
Subject: Re: mapping small parts of a pci card to conserve KVA
Date: Tue, 15 Feb 2005 14:03:12 -0700
Andrew Gallatin wrote:
I maintain drivers for a PCI card which presents itself as having
16MB of address space. Eg:
mx0: Myrinet PCIXE mem
needs to be changed to accomodate this structure, but in addition to
that a way to make statistics gathering cheaper would be nice, because
currently doing a 'vmstat -z' is really terrible for performance.
Which reminds me... those of you doing benchmarks, please don't run
'vmstat -z' while you're
On Wed, 16 Feb 2005 07:23, Warner Losh wrote:
At least on 5.3R, I seem to get back the same struct resource * from
each call. rman_get_virtual() returns a different kva for each
mapping, yet they all seem to map to the same physical address.
Eg, I call vtophys() on the results of
On Mon, Feb 14, 2005 at 02:08:07PM -0800, John-Mark Gurney wrote:
David Schultz wrote this message on Mon, Feb 14, 2005 at 08:04 -0500:
Right, databases, language runtimes, and the small set of other
applications for which it really matters usually have their own
special-purpose allocators.
19 matches
Mail list logo
