On Tue, 13 Aug 2002, Kenneth D. Merry wrote:
On Tue, Aug 13, 2002 at 21:12:59 -0400, Sergey Babkin wrote:
Kenneth D. Merry wrote:
On Tue, Aug 13, 2002 at 23:41:14 +0700, Semen A. Ustimenko wrote:
Hi!
I beg you all pardon for a question not related directly to FreeBSD, but
On Thu, 7 Feb 2002, Josef Karthauser wrote:
On Thu, Feb 07, 2002 at 03:52:26PM -0800, Terry Lambert wrote:
IIRC this problem is being addressed at a more fundamental level on
-current, by adding a 6-byte-to-10-byte READ command translator
somewhere in the abstraction layer.
On Fri, 8 Feb 2002, Terry Lambert wrote:
Gérard Roudier wrote:
A couple of READ/WRITE 6 byte commands are still mandatory for SCSI block
devices in order to accomodate softwares as boot software for example that
may not be upgradable on systems still in use.
Not a real problem, since
On Mon, 14 Jan 2002, Justin T. Gibbs wrote:
Hi all,
Currently bus_dmamap_load builds the dma descriptor in a table on the
stack.
This cause us following problems:
. our dma can be large, 1MB or more, this forces us to increase the
kernel stack size.
. our hardware would be happy
There are a couple of rules in PCI you must have in mind when
synchronization between PCI devices is needed.
1) Interrupts are not synchronization events. They just send attention to
the device driver (acts as SIGIO, for example). Some bridge may flush
posted buffers on interrupt, but
On Thu, 13 Dec 2001, Justin T. Gibbs wrote:
There are a couple of rules in PCI you must have in mind when
synchronization between PCI devices is needed.
1) Interrupts are not synchronization events. They just send attention to
the device driver (acts as SIGIO, for example). Some
On Tue, 27 Nov 2001, setantae wrote:
On Tue, Nov 27, 2001 at 06:31:31PM +0100, Gérard Roudier wrote:
On Tue, 27 Nov 2001, setantae wrote:
On Tue, Nov 27, 2001 at 06:54:17PM -, Andrey Pugachev wrote:
I am just curious, can FreeBSD kernel perform function called copy-on-write
On Tue, 27 Nov 2001, setantae wrote:
On Tue, Nov 27, 2001 at 06:54:17PM -, Andrey Pugachev wrote:
I am just curious, can FreeBSD kernel perform function called copy-on-write?
As far as I am aware, the BSD family of operating systems have always
used copy-on-write (at least since
On Fri, 9 Mar 2001, Mike Smith wrote:
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,
On Wed, 14 Feb 2001, Robert Lipe wrote:
Grard Roudier wrote:
Being smart with kernel interface is important for drivers to be fast and
reliable. Puting some stinky layer between native kernel interfaces and
drivers looks horrible to me.
Fast and reliable are both covered.
For
On Wed, 14 Feb 2001, Matthew Jacob wrote:
On Wed, 14 Feb 2001, Sergey Babkin wrote:
Matthew Jacob wrote:
The problem is that at the time this was a huge issue there were a much larger
number of machines and pieces of h/w and radically different OS's (or flavors
within Unix
Being smart with kernel interface is important for drivers to be fast and
reliable. Puting some stinky layer between native kernel interfaces and
drivers looks horrible to me.
Why isn't UDI proposed as a native kernel interface, instead?
Note that last time I read the specs, I haven't been this
On Sun, 24 Dec 2000, Peter Seebach wrote:
I may go looking. I have a passel of '875 cards that *don't* work, for
one reason or another. The symptom is, the card "probes" (it is identified
by the SRM console as an '875 rather than getting only product/vendor ID), but
the SRM console
Looks like both the NetRaid firmware and the `sym' driver are in love with
the 895. If I am right, such an evil competition obviously disallows both
of them to succeed their aim. :-)
Given this message,
Symbios,Inc.Pci boot Rom ,no supported devices found.
The Symbios BIOS seems to detect the
On Mon, 25 Sep 2000, Joe McGuckin wrote:
Is one preferable?
Here's the history:
BSD ncr - Linux ncr53c8xx - Linux sym53c8xx - FreeBSD sym
The ncr is minimally maintained mainly against O/S changes since the
latest real improvement that has been the support of 875/895/896 Ultra
chips:
-
On Fri, 15 Sep 2000, Jaye Mathisen wrote:
Compaq Proliant 5500, with the on-board NCR SCSI:
I get:
pci0: unknown card (vendor=0x0e11, dev=0xa0f0)
sym0: 875 port blahblah
sym0: no NVRAM, ID 7, Fast-20, SE, parity-checking
And the same for sym1.
What's the magic incantation to
ather not.
On Fri, 15 Sep 2000, [ISO-8859-1] Gérard Roudier wrote:
On Fri, 15 Sep 2000, Jaye Mathisen wrote:
Compaq Proliant 5500, with the on-board NCR SCSI:
I get:
pci0: unknown card (vendor=0x0e11, dev=0xa0f0)
sym0: 875 port blahblah
sym0: no NVRAM, ID 7, Fast-20, SE, p
On Mon, 3 Jul 2000, W.H.Scholten wrote:
L.s.
small addendum:
- it's fbsd 3.3R on i386 as you may have guesssed from the mail headers.
- I use the new fbsd symbios/ncr scsi driver (the README says latest
revision is sym-0.12.0-19991127).
The README file hasn't been maintained up to
On Mon, 26 Jun 2000, Mohana Krishna Penumetcha wrote:
hi,
HP-UX device driver reference manual says,
"The side-effects of any write are not guaranteed to happen
immediately. Writes are posted; they will complete eventually"
to make sure all writes are flushed from the queue,
I have made available the following `sym' driver patch for testing:
http://people.freebsd.org/~groudier/sym-1.6.0-2604.diffs
This patch is against driver version in -current. Changes are pretty
trivial and mostly nil-potent for ia32, but it seemed to me they may
need some testings,
On Sun, 28 May 2000, Mike Smith wrote:
Speaking about bus_space_*(): Does it make the thing follow the PCI
ordering rules? Very probably not since it is impossible on some systems.
There's no attempt to do this, no. However, it's possible to implement
this if there's a need.
On Fri, 2 Jun 2000, Mike Smith wrote:
Typically, a driver may want to order some operations and also not break
post buffering each time a write is performed. It may for example want to
order some operations, but not flush all writes immediately. I didn't see
how to tell bus
On Sat, 27 May 2000, Warner Losh wrote:
[ ... ]
: I donnot have NetBSD. If you can give me some pointers to relevant files
: that address the bus interface, I will try to download them and look into.
: I am only interested in the specification, so header files should be
: enough, unless a
On Sat, 27 May 2000, Jeroen Ruigrok van der Werven wrote:
-On [2527 21:06], Dennis ([EMAIL PROTECTED]) wrote:
Its seems rather humorous that the "generic" bus implementation requires
that isa drivers be hacked into the kernel with a build-time include. Very
humorous indeed. Is this a
On Sat, 27 May 2000, Warner Losh wrote:
In message [EMAIL PROTECTED]
=?ISO-8859-1?Q?G=E9rard_Roudier?= writes:
: Existing bus abstractions tend to let think that the same software driver
: can deal with different buses, bridges or IO methods without having to
: care about how these things
25 matches
Mail list logo
