On Sat, Apr 24, 2010 at 1:33 PM, Brad wrote:
...
> I have updated the diff with your suggestions.
Close: I think the #include of needs to be moved up in
sys/mman.h so that the __BSD_VISIBLE test actually works. Otherwise,
looks good to me.
Philip Guenther
On Sat, 24 Apr 2010 23:50:38 +0200
Thomas Pfaff wrote:
> On Sat, 24 Apr 2010 22:31:56 +0200
> Thomas Pfaff wrote:
> >
> > Reverting top.c to revision 1.73 and recompiling makes it work again.
> >
>
> And this diff should fix it (just an extra ; there) ...
>
Oops, forgot the second fix. Her
On Sat, 24 Apr 2010 22:31:56 +0200
Thomas Pfaff wrote:
>
> Reverting top.c to revision 1.73 and recompiling makes it work again.
>
And this diff should fix it (just an extra ; there) ...
Index: top.c
===
RCS file: /cvs/src/usr.bin
On Sat, Apr 24, 2010 at 4:33 PM, Brad wrote:
>> 4) implement posix_madvise() as a call to _thread_sys_madvise()
>>instead of madvise()
>
> Why this last one?
If a program implements its own madvise, calling posix_madvise should
do the right thing (not call the program's version). I'll look c
On Wed, Apr 21, 2010 at 09:36:45PM -0700, Philip Guenther wrote:
> On Mon, Apr 19, 2010 at 7:49 PM, Brad wrote:
> > Here is a diff to add posix_madvise() to libc.
> ...
> > -#define ? ? ? ?MADV_NORMAL ? ? 0 ? ? ? /* no further special treatment */
> ...
> > +#define ? ? ? ?POSIX_MADV_NORMAL ? ? ?
So, let's see if I'm less stupid this time.
Apr 24th snapshot. Running top(1) and using the 'g' command makes top(1)
terminate with an error message saying "top: Permission denied:". Running
it as root says "top: Undefined error:".
Reverting top.c to revision 1.73 and recompiling makes it work
Hi Alexander (and others),
I am attaching a new patch which merges your patch with another one
I have never sent to tech@ before. I shared this patch with some other
guys that were testing it, but I believe it's worth trying it again
with your modifications.
Could someone run a quick test? Agai
On Sun, Apr 25, 2010 at 03:25:03AM +0800, Alexander Vladimirov wrote:
> I actually did, your patch was the starting point, but I encountered "ath0:
> device timeout" errors while testing with both patches applied, so it still
> needs deeper research.
Great, thanks. That's valuable information ;-)
I actually did, your patch was the starting point, but I encountered "ath0:
device timeout" errors while testing with both patches applied, so it still
needs deeper research.
2010/4/25 Luis Henriques
> Hi Alexander,
>
> I was wondering whether you tested this code + my original patch. I
> just
Hi Alexander,
I was wondering whether you tested this code + my original patch. I
just merged both patches and I'm still able to use my card.
However, with my card the code you added (function ar5k_ar2425_channel)
is not actually activated -- I follow into the default case where function
ar5k_ar
On Sat, 24 Apr 2010 16:26:01 +0100
"Federico G. Schwindt" wrote:
> > + else if (hal->ah_radio == AR5K_AR2425)
> > + ret = ar5k_ar5111_channel(hal, channel);
> ^^
> shouldn't that be ar_2425?
>
Oh sorry, sure it should. I was cleaning other c
On Sat, 24 Apr 2010 16:40:37 +0200 (CEST)
Mark Kettenis wrote:
> > Date: Sat, 24 Apr 2010 16:03:50 +0200
> > From: Thomas Pfaff
> >
> > Hi.
> >
> > On my current system sysctl hw.sensors does not show anything anymore.
> > Updating /usr/src/sys to 2010-04-15 gives me back the sensors. Updatin
Here are dmesg lines for Atheros wireless in my Acer Aspire One:
ath0 at pci3 dev 0 function 0 "Atheros AR5424" rev 0x01: apic 4 int 18 (irq 11)
ath0: AR5424 14.2 phy 7.0 rf 0.0, WOR5_ETSIC, address 00:22:69:4c:f5:20
Its EEPROM reports only 802.11g mode supported which is disabled in current
kern
> Date: Sat, 24 Apr 2010 16:03:50 +0200
> From: Thomas Pfaff
>
> Hi.
>
> On my current system sysctl hw.sensors does not show anything anymore.
> Updating /usr/src/sys to 2010-04-15 gives me back the sensors. Updating
> /usr/src/sys to 2010-04-18 and the sensors are gone. Something between
> t
Hi.
On my current system sysctl hw.sensors does not show anything anymore.
Updating /usr/src/sys to 2010-04-15 gives me back the sensors. Updating
/usr/src/sys to 2010-04-18 and the sensors are gone. Something between
those two dates broke the sensors.
I'm not really sure where to go from here.
> Date: Sat, 24 Apr 2010 14:04:35 +0100
> From: Stuart Henderson
>
> On 2010/04/24 13:19, Luis Henriques wrote:
> > > Luis, can you send the latest version of your diff please. There were
> > > at least two and I'm not sure which one people should be testing.
> > > Then I'll test it on AR5213A 5.
On 2010/04/24 13:19, Luis Henriques wrote:
> > Luis, can you send the latest version of your diff please. There were
> > at least two and I'm not sure which one people should be testing.
> > Then I'll test it on AR5213A 5.9 phy 4.3 rf2112a 4.6, WOR0W which works
> > ok with the existing driver.
>
I tried drm with radeonhd driver and radeon driver. It's doesn't work. Xorg
crash at start. I can't have any readable Xorg log. I disabled radeondrm to use
X.
dmesg :
OpenBSD 4.7-current (GENERIC.MP) #535: Thu Apr 22 11:58:49 MDT 2010
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/
Hi Stuart
On Sat, Apr 24, 2010 at 11:03:21AM +0100, Stuart Henderson wrote:
> Luis, can you send the latest version of your diff please. There were
> at least two and I'm not sure which one people should be testing.
> Then I'll test it on AR5213A 5.9 phy 4.3 rf2112a 4.6, WOR0W which works
> ok wit
Luis, can you send the latest version of your diff please. There were
at least two and I'm not sure which one people should be testing.
Then I'll test it on AR5213A 5.9 phy 4.3 rf2112a 4.6, WOR0W which works
ok with the existing driver.
Other people: if you have ath(4) devices please mail the full
20 matches
Mail list logo
