On Sat, Nov 18, 2000 at 06:38:24PM -0800, John W. De Boskey wrote:
> Hi,
>
>I'm trying to increase the speed of the serial console
> on a -current box from 9600 to 38400. I've put the following
> in /etc/make.conf:
>
> BOOT_COMCONSOLE_SPEED=38400 # serial console speed
>
>
>Unf
subscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
In message <[EMAIL PROTECTED]> "Justin T. Gibbs" writes:
: 1) When mucking with mapping registers, it is best to *not* have
: io or memory space access enabled. This patch defers the setting
: of these bits until after all of the mapping registers are probed.
: It might be even bette
While working on getting the APA-1480 to work under FreeBSD's new
cardbus support, I ran into several issues.
1) When mucking with mapping registers, it is best to *not* have
io or memory space access enabled. This patch defers the setting
of these bits until after all of the mapping re
Hi,
I'm trying to increase the speed of the serial console
on a -current box from 9600 to 38400. I've put the following
in /etc/make.conf:
BOOT_COMCONSOLE_SPEED=38400 # serial console speed
Unfortunately, it doesn't work. It still runs at 9600.
I remember seeing something about t
subscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I just reinstalled from the snap server. Now, whenever I go int Xwindows,
I get wierd stuff instead of characters. It looks almost as if the fonts
have been replaced with barcodes. If I go an move the window such that it
is obstructed behind something and then move it back, sometimes the
character
On Fri, 17 Nov 2000, Andrew Gallatin wrote:
> [fxp isa irq pending but never occurs]
> I then wrote a hack which sends an eoi. If I call my hack from ddb
> and send an eoi for irq10, everything goes back to normal and the
> network interface is back.
>
> So, is it a race in the interrupt code,
Poul-Henning Kamp wrote:
>
> >> >This seems to only do the cdevsw_add if the malloc failed. I presume
> >> >this is the opposit of the intended sense. I'll fix it up if you also
> >> >think it looks wrong.
> >>
> >> If nobody have noticed in "17 months, 2 weeks ago" (as cvs-web says)
> >> that la
>> >This seems to only do the cdevsw_add if the malloc failed. I presume
>> >this is the opposit of the intended sense. I'll fix it up if you also
>> >think it looks wrong.
>>
>> If nobody have noticed in "17 months, 2 weeks ago" (as cvs-web says)
>> that labpc doesn't work, the labpc driver sho
On Sat, 18 Nov 2000 11:40:34 -0600 (CST), Jonathan Lemon <[EMAIL PROTECTED]> said:
> What version of if_dc.c
1.38
--
Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA
[EMAIL PROTECTED] [EMAIL PROTECTED]
"It's not what we don't know that hurts us,
it's wha
Poul-Henning Kamp wrote:
>
> In message <[EMAIL PROTECTED]>, David Malone writes:
> >I noticed the following while looking through the M_ZERO patches.
> >When you were cleaning up some dev stuff you made the following
> >change to labpc.c (revision 1.33):
> >
> >
> >labpcs = malloc(NLABPC
In article [EMAIL PROTECTED]> you
write:
>On Fri, 17 Nov 2000 10:30:02 -0800 (PST), John Baldwin <[EMAIL PROTECTED]> said:
>
>> what the WITNESS code does is perform extra checks on mutex
>> enter's and exit's to ensure that we aren't handling mutexes in
>> such a way that a deadlock
In message <[EMAIL PROTECTED]>, David Malone writes:
>I noticed the following while looking through the M_ZERO patches.
>When you were cleaning up some dev stuff you made the following
>change to labpc.c (revision 1.33):
>
>
>labpcs = malloc(NLABPC * sizeof(struct ctlr *), M_DEVBUF, M_NOW
On Fri, 17 Nov 2000 10:30:02 -0800 (PST), John Baldwin <[EMAIL PROTECTED]> said:
> what the WITNESS code does is perform extra checks on mutex
> enter's and exit's to ensure that we aren't handling mutexes in
> such a way that a deadlock is possible. Thus, it verifies that
> you d
15 matches
Mail list logo
