On Wed, Jul 04, 2001 at 20:18:51 -0400, Kevin Hui wrote:
Then the question is whether the kernel is copying data between userspace
and kernelspace or whether it just DMAs the data straight in/out of the
user program's address space. In Linux raw-io, given that it is a block
device and
and equipment obsolete to the rest of the world, I want to
have as clean a kernel as possible to start from.
BTW, after 2 weeks, I LOVE this OS!
Mike Smith
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Mike Smith([EMAIL PROTECTED])@2001.07.02 23:01:42 +:
=20
Be aware that ftpd is likely to be replaced in the near future, as=20
there's a strong desire to converge on the LukeM FTP tools.
no matter how nice lukemftpd looks (i got it running on several boxes
since it was the only
Be aware that ftpd is likely to be replaced in the near future, as
there's a strong desire to converge on the LukeM FTP tools.
--BOKacYhQ+x31HxR3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Mon, Jul 02, 2001 at 11:55:14PM -0400, Mike Wiacek wrote:
I was
Hi
Go to http://www.uspto.gov/patft/, search for patent number 5873127, and
you will find the description of mapping page table entries into virtual
memory via one page directory entry pointing to the page directory itself
- exactly what FreeBSD does with PTDPTDI and APTDPTDI entries on
hahahahahahaaThe patent was filed in 1996. In the 90's the patent
office starting granting patents for everything under the sun without
doing real prior art searches. I'm sure even just going to the candy
store these days is patented by someone...
Every time I tease my
So it looks like we have prior art by around 6 years, which would
invalidate the patent iff it was the same thing.
Does it mean that the algorithm is free to use by everyone or free to use
only in freebsd? I would like to implemet these page table back pointers
too and I'm scared by the
One big area we need to clean up is PNPBIOS devices. They should be
probed *FIRST* before anything else (which is hard because the isa bus
gets attached late on pci systems).
This isn't actually such a problem; the space in which PNPBIOS devices
tend to have their resources allocated is
Since some strings are non-constant (the are allocated) - I believe
the `const' qualifier in the structure declaration is incorrect.
'const' just means I will not be modifying this; it's a way for a
function prototype to constrain the function's implementation.
--
... every activity meets
| You manually set the correct I/O port in the hints file and then you
Sorry if i misunderstand, but isn't the hints file only for -current? I was
under the impression it was only to simplify driver development.
Since my goal is to clean up the driver under the newbus system, how would
I appear to have missed some of this thread. Dang.
:- Some dummy driver which grabs the resource. The dummy driver would
: need to be unloaded when the actual driver needs the resources.
:
: This sounds attractive, but it's hard to find the dummy driver when
: you want to
I don't think it would be much of a practical problem for anyone since
the old behvior can be emulated with the new md pretty easily, but
you're right that it isn't appropriate to break compatibility in
-stable. It's probably possible to retrofit the old behavior into the
new code, but I
The newbus routines use a certain amount of overhead, but once done, you
forget about it. In some device drivers, the probe methods often need to
try a variety of hardware ports. In the past, inb/outb was used, along with
an often hardcoded port address.
Does it make sense to call
| Typically, probe routines these days are invoked with a single set of I/O
| parameters to probe (and even this is only ISA devices).
|
| It's pretty rare to need to bit-bang to find a device these days anyway;
| you should probably be looking for PnP data or similar. This is what
|
| You manually set the correct I/O port in the hints file and then you
| don't have to check for each port between 0x200 and 0x3a0.
|
| Just bus_alloc_resource once and test for the card.
So without having the card for testing, i should just wrap the port access
calls into bus_xxx calls?
Some time ago, you corresponded with a gentleman from Japan (Katsushi
Kobayashi [EMAIL PROTECTED]) about his firewire code. I've also
noted a more recent query from a Wind River employee, which gives me
hope that they might have interest in pursuing it.
I don't think that Bill Paul (the WRS
Currently on FreeBSD, resources are either free, allocated or activated.
As I understand it, they mean approximately the following:
- Free: unused.
- Allocated: Resource reserved for use by device X.
- Activated: Resource actively used by device X.
This leaves somewhat of a gap.
You might also consider to get this article from http://www.ddj.com/:
Dr. Dobb's Journal March 1998 - Benchmarking and Software
Testing, Tracing BSD System Calls, by Sean Eric Fagan
AFAIR, in this article is explained what steps were necessary to make a
ptrace() for FreeBSD.
No,
Hi all,
We have a quite disapointing problem with a mylex 170 card, which causes
a system crash every 6 hours.
This card is installed in a VA Linux 2240 with 4 18GB drives, configured
in a single RAID 5 pack, running a FreeBSD 4.2-stable system.
There are known problems with the 'mly'
Hello! I'm running FreeBSD 4.3 and have encountered a mystery of some
missing files. Using find and quota to find the same files, I get
different results. For example:
...
So find is reporting 2435 files, but quota is reporting 2537. Where
could the difference be hiding?
/tmp, etc?
--
Date: Mon, 28 May 2001 19:01:37 -0500 (CDT)
From: David Scheidt [EMAIL PROTECTED]
[ snip ]
If you're really interested in database performance, remember Spindles
is good. Spreading your IO load over as many seperate disks, on as
many independent IO channels as practical will
SMAP type=01 base= len= 0009f800
SMAP type=02 base= 0009f800 len= 0800
SMAP type=02 base= 000e8400 len= 00017c00
SMAP type=01 base= 0010 len= 13ef
SMAP type=03 base= 13ff len=
Hello all,
I have been discussing on IRC with a blind people who can't use BSD
because ``brltty'', the software used to render the console tty with
braille displays, doesn't appear to work on BSD. I have been
experiencing troubles while trying to compile it and moreover, it uses
Valentin Nechayev wrote:
Sun, May 20, 2001 at 19:53:29, barry (Barry Lustig) wrote about Boot time memory
issue:
Do verbose boot (`boot -v') with large SC_HISTORY_SIZE (1000 at least,
2000 at most), and after boot check for SMAP ... lines at the very
beginning of the kernel boot
I thought it would be useful to have a sysctl for disabling the
keyboard reboot sequence. This functionality is currently
available through the SC_DISABLE_REBOOT config option, but it's
convenient to have this capability available at runtime, too.
Just edit the keymap.
--
... every
Any user who can log on at a vty can remap any key to reboot the
machine (try remapping t to reboot to annoy your firends ;-).
The sysctl can only be enabeled by root, so I think it would be
useful. A more useful sysctl might be one that prevented the
remapping of the keyboard unless you
You don't have to change anything; IRQ sharing is allowed by PCI (and in
fact, unless you change the slot the card is in, you can't change one
without changing the other).
Thanks for the reply. I first tried to change the IRQ from the BIOS. I saw
that the IRQ of both the cards changes
I'm sure this probably reeks of cluelessness, but I'm wondering how I can
find each bus in the system, and if it's PCI/ISA/whatever, so that I could
say 1 PCI bus, 1 ISA bus in system, etc. without having to probe the
system directly, since I want to make what I'm working on portable.
See
The bootstraps works with 38400, (both boot2 and loader),
but as soon as the kernel boots, it switches back to 9600.
You forgot to edit /etc/ttys to set the getty that runs on your console
port to 38400 as well.
--
... every activity meets with opposition, everyone who acts has his
rivals
Daniel Lang wrote:
What I did:
set BOOT_COMCONSOLE_SPEED=38400 in /etc/make.conf
set options CONSPEED=38400 in KERNEL
compiled and installed kernel and new bootstrap (with disklabel).
changed /etc/ttys to use std.38400 as argument to getty.
Me, too.
Same thing, just
The software I am using in Linux (cajun - cajun.sourceforge.net)
requires a serial display to work. What the linux driver does is emulate
the serial display, and provides a /dev/lcd.
As I am not a perl coder, I cannot modify Cajun to use the app you
wrote, And as I am not a C coder, I
Hi Patrick,
I didn't really explain much about the LCD+Driver...
Basically its a parallel port display that uses the generic Hitachi
HD44780
chipset. What the driver for linux does is provide a /dev/lcd
that you can address the same as you would /dev/cuaaX for a serial
matrix orbital
In message [EMAIL PROTECTED] Mike Smith writes:
: Just wondered, is there an equivelant function to ISA_PNP_PROBE that works
: with PCI (for example PCI_PNP_PROBE), anyone know?
:
: There isn't one. Go look at a PCI driver to see why.
Actually, I think he's asking for a convenience
We discussed this a while back; it has some interesting (and in some
cases) undesirable side-effects. FFS tries to balance directories across
CGs in order to balance the use of CGs for file allocation. The approach
being advocated here will tend to use CGs one at a time, resulting in
poor
Query: I've noticed that if I use up too much stack space, the freebsd
kernel (4.2) seems to crash very easily. Specially, if I create an
array of size N within a function, once the function gets invoked,
my machine just reboots. How do I find out how much stack space I've
got? I'm assuming
in a project I'm currently working on I use the access(2) call when
going through a path for plugins to load. For each : delim on the path
it does an access(2) to see if there is a file there, and then it
uses dlopen(3) to open the file as a share object, and responds
appropriatly to any
Sorry ... didn't think anyone was interested, and it's off topic, but
here it is in a nutshell:
The client I'm working with is moving from a Novell server to a FreeBSD
server using Samba. They're very unhappy with Samba's behaviour in only
1 respect: on the Novell server, files/directories
so in your oppinion it would be more preferable to either
a) attempt the dlopen(3) on each entry in the path, and give the value of dlerror(3)
to stderr for each one
or
b) attempt the dlopen(3) on each entry in the path and not give any error
information because most items would
I am developing a KLD and I am having problems getting a page fault. I am
using a set "library" (basically a set of third party object files I build
and then link in). This libarary requires its own chunk of memory that it
manages and needs to be passed a pointer to that memory (and the
I was hoping to get some useful insight before I looked into it..or if
there was a sound reason for not expanding them. Im hopeful someone
brighter will answer.
Well, if anybody but you had answered I would have fixed it right away,
but since it would probably help you if I did so I
It seems that only 256 bpf devices are supported. How painful would
it be to increase that number...I assume its an 8bit varable
somewhere?
Are there other caveats?
It's pretty trivial. Send a patch when you are done.
I was hoping to get some useful insight before
You mention that I should consider software RAID if I only need level
1. How much processing overhead is there? My system will be running
with a single 1.2GHz Athlon CPU.
Software RAID like Vinum has proven to be faster then HW
RAID. Mainly because of HW Raid card's using
On Fri, 23 Mar 2001, Daniel C. Sobral wrote:
Let me just pipe in a bit. Compromise seems just like the kind of thing
marketing or legal would want to do. The problem is that _we_ cannot
compromise because one cannot write a "half-way there" driver. It's a
technical impossibility.
I
Hey, that's not fair :-) I'd like to know how to do things the rigth way.
You'll need to tell us what it is that you're actually doing, then, since
it's hard to guess from a tiny snippet like that. 8)
Well, but if you didn't know, how could you tell that I'm doing something
very
The fpc core team is currently working on unicode support for Free
Pascal, a pascal compiler that runs on FreeBSD/i386, and I would
like to ask your opinion about what encoding to choose for the
default multibyte string type. (Delphi's WideString), choices are UTF-
8 , -16 or UCS4.
Read
Because dinking with PCI configuration space is usually the wrong thing
to do from userland.
So what about pciconf(8)?
It's a special case.
This code is used, actually, in char device driver.
Mm, so what's it doing in userspace? 8)
Did I say I'm doing it from userspace?! If
I appear to have missed the original version of this message. Oops.
Alexey
static inline unsigned long
get_kvirt_address(unsigned long address)
{
}
This function returns 0 if a virtual address is not mapped.
If you're looking at using this
Mm, so what's it doing in userspace? 8)
Did I say I'm doing it from userspace?! If I did (too lazy to dig into
sent-mail), I beg your pardon :)
Your FreeBSD sample involved making an ioctl call, so it must have been
from userspace.
Is anything wrong with using ioctl
Did I say I'm doing it from userspace?! If I did (too lazy to dig into
sent-mail), I beg your pardon :)
Your FreeBSD sample involved making an ioctl call, so it must have been
from userspace.
Is anything wrong with using ioctl calls from device driver?
Perhaps a more polite
Ioctls allow user processes to make function calls within a device
driver; they are a mechanism for exporting functionality from a device
driver out into userspace.
I know that, of course.
This wasn't clear from your example.
You don't call them from other device drivers, no.
I'm trying to write a module which should be a child of the smbus.
The smbus probe/attach is broken; you're going to have to fix it before
this code will work properly. 8(
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not
:total avail mem
Do you mean physical memory, in which case the value of hw.physmem will
tellyou.
Phys mem + swap, which I think I can calc pretty easily now
that I have swap. -sc
That's not actually a useful number either. 8)
Bear in mind, for example, that program text
Hello there,
Under linux, PCI stuff is generally done thru set of pci* functions, while
under FreeBSD there are ioctls provided by pci driver. I've been doing
some code migration from linux to FreeBSD, and got thru most of it, except
for things like this one:
You are probably doing
Hi,
i'm trying to do some programming on freebsd and i can't
find 'asm/io.h'. this must be for security reasons.
so how do i talk to the parallel port?
See /usr/share/examples/ppi, and the ppi(4) manpage.
--
... every activity meets with opposition, everyone who acts has his
rivals
THANKS! and compliments on your name. It was a quick and simple port
to see if people were interested. I've sent it to the author/maintainer
Dan Hollis but I haven't gotten a response yet. He has an email list
on Yahoo/Groups and there is occasional traffic so it isn't dead code.
Yes, I
Turning PNP on into the BIOS and recompiling the Kernel with options PNPBIOS
brings the problem back:
fxp0: could not map memory !
Turn "PnP OS" off in your BIOS. We're not ready to deal with this yet.
DES unfortunately doesn't really understand the issues here.
Rafael Tonin
-
Okay, maybe I'm missing something...
1. Has anyone tried one of these new Intel parts with BSD/OS?
2. Do any of the people involved with this have source licenses to BSD/OS?
I am quite sure BSDi hasn't been swamped with "help, my Intel card isn't
working" requests. I'm also quite sure
Out of idle curiousity, has the NIH syndrome died down enough that it might
hypothetically be possible for the three major *BSD camps to cooperate on this
kind of thing?
No, I'm afraid it hasn't.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately
Ive spoken with Mr Johnson several times. hes the biggest reason that BSDI
is what it is. Amazing that hes still there. He has no concept of what the
market wants. First he wanted to challenge microsoft (at similar prices)
for the server market now he wants to be redhat. funny guy.
What board is this?
If this is the board I think it is, it's a Supermicro P6DLE dual Slot-1
motherboard with an integrated Intel 82559 (no external PHY).
(I had this board for some time before I gave it to David, it was
originally donated to FTL by Bob Willcox.)
Sam
- Original
Joe; it looks like you have some funny ideas about something that's not
actually very relevant. I assume that you have already gone and bought
Monster Cable(tm) SCSI cables, and that you have the special
oxygen-free-copper SCSI controller PCBs, because none of this is going to
mean anything
I think its been mentioned several times in this and other threads that
intel has a driver for LINUX that is effective documentation on the board,
and the code is public (although you may have to stick an intel copyright
in the code also).
It hasn't been mentioned in this thread that
The point here seems very simple. The intel NICs are on a large number of
MBs and the eepro100 is the most popular card on the market. So why is
there vitually no maintainer for arguably the most important driver in the
freebsd tree when there are maintainers for scads of obscure, must
maybe commercial vendors would be willing to fund some freebsd projects if
there was a positive relationship.
They do, and there is. I'm continually irritated that we can't work out
a better relationship with you/ETinc, since I think it'd be to our mutual
benefit. You're just one of those
In message [EMAIL PROTECTED], Dennis writes:
I really dont care to ask this on the list, but DG doesnt answer my private
emails, so I have little choice.
Yup. None at all. I mean, you're getting something for free, and the
people giving it away don't seem to be able to build their
In message [EMAIL PROTECTED], [EMAIL PROTECTED] writes
:
is mkdir(3) guaranteed to be atomic?
Yes.
Um. mkdir(2) is atomic. Note that mkdir(1) with the -p argument is
*not* atomic.
Are there filesystem type cases where this might not be the case
(NFS being my main concern )
In message [EMAIL PROTECTED], Mike Smith writes:
How would it *not* be atomic?
Well, imagine a hypothetical broken system in which two simultaneous calls
to mkdir, on some hypothetical broken filesystem, can each think that it
"succeeded". After all, at the end of the
To follow up on myself, it seems to work on older Asus P2B-LS
motherboards (onboard fxp). But only after you shutdown FreeBSD via
'shutdown -p now'. I don't suppose anybody knows which machines
support this well?
The machine *should* support WOL from a cold power-on. However, I do get
Hi
I am trying to convert my PCI device driver into a KLD.
So far I have done the following:
1. Built the kernel without the static linked device driver.
2. Added entries to Makefiles in /sys/modules and /sys/modules/xxx.
3. Did "make all install" in /sys/modules directory.
4. Tried
Is it true that freebsd can't boot from a zip drive?
No.
You can't boot from the parallel-port drives, but that's a feature of the
PC not expecting to be able to boot from a printer rather than a FreeBSD
issue.
I've personally booted FreeBSD from the old, old ATA Zip drives, the
ATAPI
You can't boot from the parallel-port drives, but that's a feature of the
PC not expecting to be able to boot from a printer rather than a FreeBSD
issue.
I've personally booted FreeBSD from the old, old ATA Zip drives, the
ATAPI ones and of course the SCSI drives, in both whole-disk and
I'm trying to convert a PCI network interface device driver to a KLD module.
However, the driver is depending on a pseudo-device and the pseudo-device is
in turn dependent on the device driver. How do I specify dependencies
between KLD modules and what type of module shall they be?
With a
I am trying to convert my PCI device driver into a KLD.
So far I have done the following:
1. Built the kernel without the static linked device driver.
2. Added entries to Makefiles in /sys/modules and /sys/modules/xxx.
3. Did "make all install" in /sys/modules directory.
4.
when it comes to ibm, as far as i understand you have to hook up their
filers to rs/6000(aix) or s/370 or s/390 systems since they are "only"
fibrechannel or ficon attached raid subsystems, so the client platform
is responsible for handling all the filesystem stuff.
Hrrm. The last box I
Unless the network is lying to me again, Lyndon Nerenberg said:
Another company to look at is Yottayotta (www.yottayotta.com).
Yeah, and they have a theme song...
http://www.yottayotta.com/images/YottaYotta_Song.mp3
Or is that a reason *NOT* to look at their product?
Heh. The
I've just finished scouring Cisco's documentation, and it doesn't look
like FEC is anything beyond plain old trunking (with the option of
autoconfiguration on some hardware). As long as you configure the
appropriate ports on the switch on the other end as "SA-Trunk", or
"Trunk", you should
WHo would I contact for support for freebsd for that driver?
Emulex, as they don't offer source or documentation for the hardware.
You may want to look at a Qlogic-based controller instead.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately
I have about 10 min to make decision on OS of this boxi hate linux but
I may have no choicei have to get this up as an nfs server by the end
of the day.
Solaris. Forget Linux for NFS service.
--
... every activity meets with opposition, everyone who acts has his
rivals and
I have been poking around my kernel for quite some time now, and I have
been doing it with various text editors and programs of that nature. It
suddenly occured to me that there might be a better way to go about
this. So I ask you, are there any programs that make reading and editing
the
The BIOS trace says the PXE is revision 2.0, build 68 : is there some other,
perhaps better version of it ? (the on-board NIC on the machine is an fxp)
Build 068 is a disaster; you ideally want 082 or later.
is there some standard way to upgrade the pxe code on the cards ?
in case,
The BIOS trace says the PXE is revision 2.0, build 68 : is there some other,
perhaps better version of it ? (the on-board NIC on the machine is an fxp)
Build 068 is a disaster; you ideally want 082 or later.
PS : As I've seen, rc has been modified to get rid of
"early_nfs_mounts". After
:| The files are accessed approximately 3 or 4 times a day on average.
:| Older files are archived for reference purpose and may never
:| be accessed after a week.
:|
:| Ok, this is a start. Now is the 70 TB the size of the active files?
:| Or does that also include the older
In message Pine.BSF.4.21.0102012248001.7223-10@localhost, Max Khon writes
:
what does the following error message mean:
swap_pager: indefinite wait buffer: device: #ad/0x20001, blkno: 288,
size: 4096
it happens when burncd is fixating disk
My intuitive guess is that the fixate
The memory areas "appear" to be fixed relative to each other:
mem1 == base + 0x00 (size==0x20)
mem2 == base + 0x201000 (size==0x000100)
mem3 == base + 0x203000 (size==0x000400)
So of course, it is tempting to wonder whether it is really neccessary
to allocate three
on Thu, 25 Jan 2001 Mike Smith wrote:
__dtoa has static locals. Bad function, no biscuit.
I think this can be a serious problem for any threaded application,
I have not tested your patch yet, you think this is only a temporary
solution right? Have you commited this patch to current
* Alexander N. Kabaev [EMAIL PROTECTED] [010125 12:16] wrote:
Will functions marked with __attribute__((__constructor__)) or
__attribute__((__destructor__)) satisfy your needs?
Compiler will insert calls to these functions gets into .init section of the
resulting ELF module which in turn
(Please trim cc's on any followups to remove -hackers, thanks.)
I'm happy to announce a quick public BETA cycle for the 3ware 3DM
management utility for their family of ATA RAID controllers and FreeBSD.
3DM allows you to monitor and repair RAID arrays on 3ware controllers
using a web
After upgrading to FreeBSD 4.2(from 4.1) and MySQL 3.23.32 (from 3.22.32), I
kept seeing mysqld crashes after a few minutes of heavy load. I traced it
down to one rather situation. Every time it crashed, I was getting a
segfault inside __dtoa (which was called by sprintf). If I looked at
I think he's refering to the 82559 manual. It is available from Intel to
developers, but only with an NDA. For various reasons, I can't sign an NDA
for that information without putting myself in legal jeopardy. That has always
been true, but I was able to obtain the [now older] 82557
What is "IP Address
overtaking"?
It is a way to move IP address from one host to another, it is used for
redundancy purposes. If one host goes down the second take over.
Commonly referred to as "IP failover".
--
... every activity meets with opposition, everyone who acts has his
Primarily for two reasons: 1) I didn't know that Intel had released Linux
driver source, and 2) I don't have any boards that don't work correctly.
I don't either, anymore, sorry. 8(
I'll look into the Linux driver, however, and see if it has anything
useful in it. Historically the
OK, one of my biggest pet peeves of late is that unless you have the PS/2
keyboard plugged in at boot time, it's not recognized.
Change the flags value for the 'atkbd' driver to 0.
The default value, 0x1, is necessary for the correct functioning of
systems with USB keyboards.
--
... every
I'm calling contigmalloc() with M_WAITOK. For every contigmalloc, I
have a corresponding contigfree(). But after a few thousand cycles,
contigmalloc() starts returning NULL. It self-destructs in about 3
minutes. I see the same behaviour with M_NOWAIT. As an aside, WAITOK's
should never
Is there an s/g memory interface in FreeBSD? This was my first choice,
but since I couldn't find a set of functions to build a list of buffers
that satisfied a set of constraints, I fell back to contigmalloc to get
things off the ground. I'd be delighted to use an interface to get me
If busdma is "pretty broken" for network-sized requests, I may just
avoid it for now, implement the contigmalloc cache, and move on to more
interesting problems.
It's broken for network-sized requests because it uses contigmalloc. 8)
The cache approach will work equally well for either
In message 3A6B3B82.15538.103246@localhost "Marco van de Voort" writes:
: Does FreeBSD have any possibility to this?
See /dev/io.
Much better to use i386_get_ioperm/i386_set_ioperm.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents
The short answer to your question is "no". You might want to talk to the
TrustedBSD people, though, since the access control mechanisms are
effectively the authentication side of resource control, and the gates
that they are implementing could become part of a wider "resource"
management
The bug was solved and it was because the BIOS advertises wrong interrupt
line. It should be 5, not 12. So I registered ISR for line 12, of course
never triggered.
Er, can you be more specific here? Where is the interrupt line
"advertised"? Is the BIOS incorrectly populating the intline
I load the driver the first time, and it loads correctly. I unload it and
reload it and it attempts to attach twice (with the exact same resource
values). I unload and reload it and it attempts to load 3 times, unload/reload
... 4 times (you see the pattern). If I load the second module I
What exactly is the hardware problem..and if you've identified it why is
there no simple workaround after all this time (or is there)?
You should read the i8259 datasheet, or the datasheet for any device
embedding a macrocell which emulates it, and once you read the section on
spurious
101 - 200 of 779 matches
Mail list logo
