On Thu, 13 Jun 2002 15:37:55 -0700 (PDT)
Gordon Tetlow [EMAIL PROTECTED] wrote:
I've imported the excellent work by Mike Makonnen into the tree. Please
note that it should be fully functional but there are some parts that need
some looking at:
atm
ipfilter
some others that I'm
the r/e uid, and touch just those that
already dealt with the uidinfo.
In any case, I'll submit a patch to you doing it the way you suggested.
Cheers,
Mike Makonnen
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
to go:
I like your idea better, because it is less work and less bloat. Sometimes
I have to keep reminding myself: Choose the simplest design that works.
Cheers,
Mike Makonnen
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
, and not very complex
either).
Do you like it?
Should I go ahead and implement a patch?
Anything I overlooked?
Cheers,
Mike Makonnen
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
to this to use M_NOWAIT and continue re-trying untill it
succeeds? Is there on-going smp work in locking down struct proc that
will eliminate this problem?
Cheers,
Mike Makonnen
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
a missing
2/dev/null somewhere.
Cheers,
Mike Makonnen
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Sat, 08 Jun 2002 10:57:31 -0400 (EDT)
John Baldwin [EMAIL PROTECTED] wrote:
Heh, that's fine. Let me know if it works. :)
Ok, no more exhausted messages. Before I applied it I had a bunch
of dead witnesses when I did a show witness in ddb (i.e. - only about
1 out of 10 witnesses
appreciate it if people with the appropriate setups especially test
the following:
ATM
ipfilter
amd
Any comments, constructive criticism welcome.
Cheers,
Mike Makonnen
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
[ forgive this breach of net-ettiquette, but this should probably be
given a wider audience]
On Thu, 06 Jun 2002 05:01:18 -0600
Mike Makonnen [EMAIL PROTECTED] wrote:
Ok folks,
I have our current rc.* scripts ported to the NetBSD framework.
Preliminary testing says it's good to go, so
I have been trying for several days now to access current.freebsd.org so I
can get the latest -CURRENT snapshot instead of my usual DP1 - cvsup -
buildworld, but I am unable to get in.. Is this not a public server?
saturn# ftp current.freebsd.org
Connected to usw2.freebsd.org.
220
to _BYTE_ORDER and friends, so that even confussed
applications work.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
+#if !(defined __osf__ defined __alpha__) !defined __NetBSD__ !defined
+__FreeBSD__
#define __EXTENSIONS__
#define _POSIX_C_SOURCE3 /* This is for Solaris. */
#definePOSIX_C_SOURCE3
%%%
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED
, after
which it began to return garbage (I'm pretty confident that my program
didn't have a buffer overrun, it was a fairly short simple effort)
Would it be possible for you to reproduce the source to a small
program that demonstrates the problem?
Best regards,
Mike Barcroft
To Unsubscribe: send
be cool is if the man pages were somehow integrated
into the FreeBSD Documentation Project. That way I have to remember only
the SGML tags.
(yes, yes, I know: patches please? 8-)
In any case, here's a proper patch (man page and all):
http://home.pacbell.net/makonnen/rmuser.diff
Cheers,
Mike Makonnen
On Fri, 2002-05-10 at 02:56, David O'Brien wrote:
On Fri, May 10, 2002 at 01:56:16AM -0600, Mike Makonnen wrote:
The problem with writing man pages is, if you don't do it often enough
you keep having to relearn it every time you do (which is why I wised up
/usr/share/examples/mdoc/example
of the new expr(1) is wrong.
Not according to the Standard, or the response from Garrett's request
for clarification of the Standard.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
before it defines this union, so
something must be broke in there.
Yes, sys/cdefs.h wasn't being included on some archs. It should be
fixed now. Sorry about the breakage.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
Ruslan Ermilov [EMAIL PROTECTED] writes:
I see the same breakage here.
The breakage has nothing to do with -Werror. Recent commit by
Mike Barcroft to sys/*/endian.h is the culprit.
But the actual problem is with gdb. After a lot of experimenting
I've found that contrib/gdb.291/gdb
David O'Brien [EMAIL PROTECTED] writes:
On Fri, Apr 12, 2002 at 12:12:12PM -0400, Mike Barcroft wrote:
I think machine/endian.h would be better here. It may not have
worked because of the missing sys/cdefs.h issue.
We will never get that header included in the GDB sources
Mike Barcroft [EMAIL PROTECTED] writes:
Sort of. The way it historically built was by taking advantage of the
fact that C allows multiple #define's if they are the same. My commit
changed the definition of BYTE_ORDER to _BYTE_ORDER instead of
LITTLE_ENDIAN or BIG_ENDIAN.
Just a little
_XOPEN_SOURCE
Peter fixed this a day or so ago; see rev 1.51.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
^
: - cleanup
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
subscribe
_
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
(this should be fixed by Sunday).
If someone can provide a compiler error and source file, I can
figure out what the problem is.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
as
well. netinet/in.h needs to come first.
This is untrue. arpa/inet.h can appear before netinet/in.h or
vice versa (remember to include sys/types.h before netinet/in.h,
since netinet/in.h isn't a POSIX-2001 header yet).
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED
might be fatal in C++. If this
is the case, my new endian patch will fix this. Try compiling KDE
after installing a world with the following patch applied:
http://people.FreeBSD.org/~mike/patches/endian-ng3.diff
I plan on committing this on Sunday.
Best regards,
Mike Barcroft
To Unsubscribe: send
, but requires pollution from
another header, so I used the __uint32_t variant.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
you decide to go with.
cheers,
mike makonnen
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Thu, 2002-02-28 at 09:02, Terry Lambert wrote:
Thanks for the hard work, Mike!
Thanks, nice to know someone appreciates it. Every one has their own
ideas about how it _should_ be done, so I expected I'd get flamed for
not pleasing everyone. OTOH it's been less than 24 hours since I posted
On Thu, 2002-02-28 at 09:23, David O'Brien wrote:
On Thu, Feb 28, 2002 at 08:39:33AM -0800, Mike Makonnen wrote:
I chose to go a slightly different route than Gordon, in that I have not
tried to make the scripts compatible with NetBSD (His scripts include
conditionals for NetBSD, mine
FWIW, now that Peter has temporarily backed out his pmap-related changes,
-current has stabilized again. Those who were having trouble with panics
on boot (or within a few minutes after) with kernels built during the last
day or two should definitely cvsup.
Mike Silby Silbersack
I'm experiencing the same double panic on boot that PHK is now; are we the
only ones, or is it just that nobody else has updated recently?
Mike Silby Silbersack
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Tue, 26 Feb 2002, Peter Wemm wrote:
Mike Silbersack wrote:
I'm experiencing the same double panic on boot that PHK is now; are we the
only ones, or is it just that nobody else has updated recently?
If you are not using acpica, then you're probably using vm86 for pcibios
calls. I've
On Tue, 26 Feb 2002, Mike Silbersack wrote:
I reverted that change, and the double panic still occured. :|
FWIW, you're correct in that I'm not using the acpi module.
Mike Silby Silbersack
Using ACPI doesn't help here either. Hmph. Can I get a kernel dump that
early in the boot process
On Tue, 26 Feb 2002, David Wolfskill wrote:
Date: Tue, 26 Feb 2002 19:46:59 + (GMT)
From: Mike Silbersack [EMAIL PROTECTED]
Using ACPI doesn't help here either. Hmph. Can I get a kernel dump that
early in the boot process? The dumpon manpage doesn't suggest a way as
far as I can
On Tue, 26 Feb 2002, Peter Wemm wrote:
Mike Silbersack wrote:
Hm, sounds like UP got optimized out.
Gah! That would be a first. :(
Well, until I can build a working kernel, I'll just assume that it's a
feature.
Mike Silby Silbersack
To Unsubscribe: send mail to [EMAIL PROTECTED
changes of the last two days
seems like a good idea.
Mike Silby Silbersack
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Wed, 27 Feb 2002, Mike Silbersack wrote:
Disabling PG_G allows it to work here again as well. Given the problems
we're experiencing, backing out the pmap changes of the last two days
seems like a good idea.
Mike Silby Silbersack
Well, I sorta take that back. The box has been up
[] = blah;
char baz[] = foo;
cheers,
mike makonnen
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
the old flags, and
indicate that they are deprecated in the man page.
Deprecated features should generate warnings. See the Committers
Guide (8.3) for details. The change to the manual is correct though.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
Doug Barton [EMAIL PROTECTED] writes:
Mike Barcroft wrote:
Deprecated features should generate warnings.
Ok, then let's call it Undocumented legacy support. I agree that
features we don't want to support anymore should generate warnings that
encourage users to change. However
://developer.intel.com/technology/iapc/acpi for more details.
There aren't many changes in the FreeBSD-specific code, this is just
catching up with major improvements in the interpreter.
As usual, please report any problems or success to the list.
Regards,
Mike
To Unsubscribe: send mail to [EMAIL PROTECTED
) Commit them.
If you aren't interested in doing this, you are the sole person to be
blamed for them not being integrated into FreeBSD.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Terry Lambert [EMAIL PROTECTED] writes:
Mike Barcroft wrote:
I'm getting sick of reading this. Terry, if you want this code
integrated into FreeBSD, here's what you do: 1) Find yourself a
mentor, 2) Get a commit bit, 3) Update worthy patchsets to -current
sources, 4) Have them reviewed
the necessary functionality to do
this, so I was thinking that I might be able to simulate such an effect by
putting a null pointer reference right before such calls, thereby creating
a panic. Is this the best way to go, or is there some easier way to
accomplish a similar effect?
Thanks,
Mike
On Thu, 14 Feb 2002, Bruce Evans wrote:
On Thu, 14 Feb 2002, Mike Silbersack wrote:
I've been poking around in ddb in an attempt to work on some forkbomb/low
memory problems, and I've found it extremely useful. There's one thing I
can't figure out how to do that would be useful, though
regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
to machine code? 2, 3, 4 people? How hard is it to
use `pkg_add -r' and rearrange your PATH to make a stock GCC work?
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
notice that some people were wasting a developer's time
when the project as a whole needs it much more. I'm talking,
ofcourse, about the imminent GCC upgrade that David is working on.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
-existing data repositories (LDAP,
CVS, file system, etc.) and could be processed and edited using a number
of standard tools.
If only I had not run out of time write it, I'd be happily using this today.
Mike.
--
Mike Gratton [EMAIL PROTECTED]
Every motive escalate.
Blatant self-promotion: http
do not
commit any stronger WARNS levels to Makefiles.
Alternatively, developers working on WARNS could use a newer GCC from
the ports collection.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
as well.
mike
--
Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
.
*** Error code 1
Stop in /work/src.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
. It would require
reworking the comments in the files in /etc/defaults, and a little
more discipline in editing them, but that's not necessarily a bad
thing.
mike
--
Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant
on a preemptible kernel?
That's the plan.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
toolchain suffers from this problem, so a
number of files on the sparc64 p4 branch have custom versions.
Anyway, I'm told this problem has been fixed in 3.1, which is the
planned version of GCC for 5.0-RELEASE.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
oh, well. They say something along the lines of
Disk error: lba is 0x9 (should be 0x10)
or similar. then it trys to boot the kernel twice using the loader, but
fails with the path 0:fd(0,a)/kernel
i tried it in vmware with the same results comming right from the image.
mike
On Thu, 17 Jan
no problem.
keep up the good work.
mike
On Thu, 17 Jan 2002, Ian Dowse wrote:
In message Pine.LNX.4.21.0201170805060.3093-10@dosmonos, Mike Brancato wr
ites:
oh, well. They say something along the lines of
Disk error: lba is 0x9 (should be 0x10)
or similar. then it trys to boot
seems to work in vmware now.
maybe i'll cvsup my source and rebuild my machine tonight. fun.
thanks.
mike
On Thu, 17 Jan 2002, Ian Dowse wrote:
In message Pine.LNX.4.21.0201171724390.5037-10@dosmonos, Mike Brancato wr
ites:
no problem.
keep up the good work.
mike
Ok, it's fixed
Just leting you guys know that the Jan 15th and Jan 16th boot floppies
aren't working. the Jan 13th snaps are though.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
to `linux_ifname'
*** Error code 1
A few days ago changes were made to sys/compat/linux/linux_ioctl.c (rev. 1.79, I
believe) that removed linux_ifname(). Just checkout rev. 1.78 and use that instead.
cheers,
mike makonnen
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd
. Everything except the ident string should succeed.
cheers,
mike makonnen
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
be eliminated.
Once this conversion is complete, the per-module namespace will behave
consistently within the kernel as well.
Questions and comments welcome.
Regards,
Mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
just a detail.
Regards,
Mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
*one* 'case ${nfs_client_enable}'.
Look at the implementation of case ${nfs_server_enable}, earlier in rc.network for an
example of how it should be done.
Cheers,
mike makonnen
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
You should read UPDATING.
PROCFS now requires PSEUDOFS.
mike makonnen
On Tue, 8 Jan 2002 23:48:44 -
ADRIAN.BROWNE [EMAIL PROTECTED] wrote:
Anyone got any ideas
kern.version: FreeBSD 5.0-20020102-CURRENT #0: Wed Jan 2 12:00:48 GMT 2002
make failed on
/usr/src/sys/i386/compile
to upload, and overwrite a file, you might try setting up a restricted
user for this purpose, that only has write access to a single directory.
Mike
--
Mike Heffner mheffner@[acm.]vt.edu
Fredericksburg, VA [EMAIL PROTECTED]
msg33416/pgp0.pgp
Description: PGP signature
On 05-Jan-2002 Riccardo Torrini wrote:
| On 05-Jan-2002 (19:47:53/GMT) Mike Heffner wrote:
|
| I noticed a strange behaviour, sending a file twice create
| version even if sunique is off, on all versions I can test.
|
| This is intentional...
|
| This is black magic. I hate it. I hope
explicit package name at ./@/kern/vnode_if.pl
line 98.
Execution of ./@/kern/vnode_if.pl aborted due to compilation errors.
Bruce
Crap. Ok, working on it.
Mike Silby Silbersack
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
) || defined(__OpenBSD__)' section. If you are
interested in the types that used to be defined there, they are now in
sys/stdint.h.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
I upgraded by cvs on saturday night,
Sunday I didn't use it.
Monday I tried to boot it. but the loader says:
ASSERT mumble
and the system reboots
I'd LOVE to know wha the assert is but really My opical neurons take at
least 20mSecs to fire and by the time I've found the Asssert line
I'm
On 29-Dec-2001 John Hay wrote:
| This patch works just fine here, thanks.
|
| Any chance of getting it as part of lukem distribution or ours?
|
Luke has incorporated it into NetBSD's ftp, and it will be included with
the next import of lukemftp.
Mike
--
Mike Heffner mheffner@[acm
with unwanted messages.
Any idea?
AFAIK, this was fixed. Check the commit logs for sh(1).
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On 19-Dec-2001 Manfred Antar wrote:
| mail dumps core on current with latest /usr/src/usr.bin/mail updates:
|
Argh, I forgot braces around a 'for' loop. This has been fixed by Andrey in
rev. 1.12 of send.c.
Mike
--
Mike Heffner mheffner@[acm.]vt.edu
Blacksburg, VA [EMAIL
subscribe freebsd-current
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Hi all
Glad to hear that it worked for you.
Just wondering..is your affected motherboard using AMI for BIOS?
Mine is AMI too.
I'll try to submit a PR. Hopefully the fix will be accepted.
A PR that hardwires IRQ 12 probably won't be accepted. Can you look
around the ACPI tables and
You can define ACPI_DEBUG in the environment before building the kernel,
or when manually building the module, or in /etc/make.conf.
I've stumbled on the ACPI_DEBUG issue in the module load as well.
The ACPI_DEBUG definition only propogates to the opt_acpi.h file
in the base kernel. The
should not be used in
build tools. Perhaps he would be so kind as to back out the offending
code.
Any suggestions?
I would recommend removing the __FBSD() line locally until this has
been resolved.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd
On 13-Dec-2001 Mike Heffner wrote:
| mikeh 2001/12/13 15:46:45 PST
|
| Modified files:
| usr.bin/ftp Makefile
| Removed files:
| usr.bin/ftp cmds.c cmdtab.c complete.c domacro.c
| extern.h fetch.c ftp.1 ftp.c ftp_var.h
On 14-Dec-2001 Mike Heffner wrote:
|
| Differences/Losses:
|
| *) FTP_PASSIVE_MODE vs. FTP_MODE
s/FTP_MODE/FTPMODE
As a followup clarification, ftp(1) will attempt to use passive mode by
default, and fall back to active mode. To achieve the old default behavior
(active mode) set FTPMODE
Still, it's my opinion that these BIOSes are simply broken:
Joerg's personal opinion can go take a hike. The reality of the
situation is that this table is required, and we're going to put it there.
The reality of the situation is far from being clear. The only thing
I can see is
What is it about this particular topic brings out such irrational
emotions in you and others?
Because you define as irrational those opinions that don't agree with
your own. I don't consider my stance irrational at all, and I find
your leaps past logic and commonsense quite irrational in
Joerg Wunsch wrote:
I guarantee you that there are a number of controllers which have
different ideas of how to do soft sector sparing _at the controller
level_ rather than at the drive level.
We have dropped support for ESDI controllers long since. :-)
Seriously, all the
: IBM DTLA drives are known to rotate fast enough near the spindle
: that the sustained write speed exceeds the ability of the controller
: electronics to keep up, and results in crap being written to disk.
I would adssume it actually the tracks FURTHEREST from the spindle..
As Peter Wemm wrote:
There shouldn't *be* bootblocks on non-boot disks.
dd if=/dev/zero of=/dev/da$n count=1
Dont use disklabel -B -rw da$n auto. Use disklabel -rw da$n auto.
All my disks have bootblocks and (spare) boot partitions. All the
bootblocks are DD mode. I don't
(The other day a coworker of mine wanted to use DD for some IBM DTLA
disks, because he'd heard that the disks performed better that way -
something to do with scatter-gather not working right unless you used
DD. I'm highly skeptical about this since I have my own measurements
from IBM DTLA
,
parameters are controlled via the driver's ioctl interface.
You should be able to find good examples of this in the source for other
drivers similar to your own. If you have more specific questions, please
feel free to ask them here.
Regards,
Mike
--
... every activity meets with opposition
On Sunday, 9 December 2001 at 19:46:06 +0100, Joerg Wunsch wrote:
personal opinion
Still, it's my opinion that these BIOSes are simply broken:
Joerg's personal opinion can go take a hike. The reality of the
situation is that this table is required, and we're going to put it there.
End
and /usr/ports trees.
Any ideas?
What, you've never heard of giving a 110%? :)
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
as a part of a crunched binary.
Should be fixed now.
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
I don't know if there's a way to stop this, but it's normal, whenever I use
my Parallel port zip drive, I have similar problems.
There isn't, really. The parallel port is terribly inefficient.
But what surprises me is that copying that data to the parallel intfc burns
up an incredible
: As a workaround for you, though, try adjusting the memory that the driver
: requests for the register window to be based at 0xf400.
Actually, for most people, just ignoring the error is enough to make
it work.
This bothers me. Are bridges ignoring their mapping registers?
--
: : requests for the register window to be based at 0xf400.
:
: Actually, for most people, just ignoring the error is enough to make
: it work.
:
: This bothers me. Are bridges ignoring their mapping registers?
It would appaer that they are. It hurts my brain that it works.
i found a posting on the netbsd current mailinglist stating that with some
minor modifications it sort of attached to the umass driver, but the author
had no further success. the posting can be viewed at:
http://www.geocrawler.com/archives/3/497/2001/7/100/6233506/
hope someone with the
In message [EMAIL PROTECTED] Nickolay Dudorov writ
es:
: And I can buildkernel only after the next patch:
I just removed this from build until Mike can fix the ciss driver
itself.
Sorry about this; I got distracted last night, and my last -current
test build was too long ago. 8( I'll
So this means the output queue on my net card is full, right? And I guess
there is no easy solution... Oh well, I'll have to cope.
That's correct; the pipe is full, and you can't put any more bits in it.
Typically you run into this situation when your app is generating more
data than can
hi all,
this patch will put an end to those XXX lines in the
NOTES file, which were regarding uncategorized
options.. such as USERCONFIG etc.
I am also attaching a tar.gz package which has the
patch compressed and archived.
This is NOT how to do this.
File a PR containing the patch,
I'd like to get card bus working, however under 5.0-current my pcmcia
controller is failing to load with the message:
pccbb0: TI4451 PCI-CardBus Bridge at device 15.0 on pci2
pcib2: device pccbb0 requested unsupported memory randge
0x1000-0x (decoding 0xf400-0xfbff,
The build and all goes well, but after a reboot. the kernel boots and
just hangs on the acpi_cpu and refuses to go further.
deleting the acpi.ko in /boot/kernel solves the problem for me. Is there
any way to _disable_ acpi all together? I tried doing it from the boot
menu (using unload and
601 - 700 of 1809 matches
Mail list logo
