It seems Mike Smith wrote:
But hey, I don't have the time to work on ATAPI. Soren does, so he gets
to call the shots.
Right :)
... so we lose. 8(
Well, depends on POV I guess...
Soren, please take a little time to understand what Justin is talking
about. The parts of CAM that
It seems Justin T. Gibbs wrote:
My main complaint so far about the new ATAPI stuff is that it duplicates
or lacks (assuming it will be implemented) much of what CAM would have
given for almost free:
- Interrupt driven configuration
That there allready, if we mean the same thing here.
It seems Christopher J. Michaels wrote:
Well, I'm sorry to say that it looks like I've found the answer to my own
question. I found after this posting (by looking at dmesg) that I was
getting the following error.
acd0: rezero failed
I did some searching and found several postings in
It seems Justin T. Gibbs wrote:
In article 199903171205.naa25...@freebsd.dk you wrote:
It seems David O'Brien wrote:
Boot from an ata disk on major# 30, device name ad, plain and simple.
Does this mean ata disks won't come under CAM/da ?
Not if I can help it :)
It could be done
It seems Justin T. Gibbs wrote:
In article 199903171103.naa13...@ceia.nordier.com you wrote:
Søren Schmidt wrote:
OK, easy enough, this is what I want to do:
Boot from an ata disk on major# 30, device name ad, plain and simple.
I'd be inclined to handle this outside the
It seems Sheldon Hearn wrote:
Hi folks,
19990316:
The name of the old wd.c and atapi.c based CDROM driver has
been changed back to wcd. So update your config file to use
device wcd instead of device acd.
Am I right in thinking that this only applies to people
It seems Robert Nordier wrote:
If the problem is the bootblocks, why not send a message to Robert
Nordier, or if it's loader, to Mike Smith or Daniel Sobral? And
say, This is what I want to do, what are we going to do about it?
or something similar?
OK, easy enough, this is what I want to
It seems Robert Nordier wrote:
Søren Schmidt wrote:
OK, easy enough, this is what I want to do:
Boot from an ata disk on major# 30, device name ad, plain and simple.
I'd be inclined to handle this outside the boot code, by treating the
passed in major# as describing the device
It seems David O'Brien wrote:
Boot from an ata disk on major# 30, device name ad, plain and simple.
Does this mean ata disks won't come under CAM/da ?
Not if I can help it :)
It could be done by slamming a translation layer ontop of the existing
wd driver or of cause on top of the new I'm
It seems Matthew Jacob wrote:
I asked Soren just this kind of question, and he declined to answer. I
doan geddit...
WHAT ??
I replied with this:
#From sos Wed Mar 17 08:51:14 1999
#Subject: Re: How to add a new bootdevice to the new boot code ???
#In-Reply-To:
It seems Robert Nordier wrote:
OK, I'll add it to the bootblocks.
Incidentally, while I'm in there and thinking about it, I'd quite
like to fix the boot code to boot from LS-120 drives at the same
time. So if anyone has one of these, and wouldn't mind spending
some time running a few bits
It seems Daniel C. Sobral wrote:
Søren Schmidt wrote:
Well, that breaks somewhere else, as the mount code is clever enough
to look at the name of the driver in this case ad which doesn't
match the specified #0 ie wd.
I kindof tried this by having my driver put itself in both the
wd
It seems David O'Brien wrote:
People are asking for:
wd0, ...
da0, ...
Ie, join ad and da namespaces.
If you want to join anything, go directly to disk%d instead.
But that is not the deal that was presented to us when we had to endure
the gratuitous sd-da name change. The
The name of the old wd.c and atapi.c based CDROM driver has been changed
back to wcd. So update your config file to use device wcd instead of
device acd.
This is to avoid confusion with the new ATA/ATAPI system.
MAKEDEV has also been changed to reflect this, and to support
the device nodes of
It seems Pete Mckenna wrote:
Do the AIWA bolt and Sony superstation tape drives work with the new
ATA/ATAPI driver or the old drivers ?
I've been following Soren's posting on the new driver but haven't seen mention
of this, and saw on linux lists that they seemed to be writting specific
It seems Pete Mckenna wrote:
Soren,
Here's what Aiwa has to say;
BOLT utilizes an ATAPI (IDE) interface. It connects to an existing IDE
interface
as either master or slave. To configure, simply enter a single jumper
setting.
AIWA BOLT uses Travan drive hardware and records on Travan 3
So here I am with our new boot code and a new device, how the
@$ am I supposed to boot from that with the glory new
boot blocks, forth and what have we ???
If my suspicion is right, the glory fades pretty damn fast...
-Søren
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe
It seems Maxim Sobolev wrote:
Driver works fine, but on my notebook, when HDD awake from sleep I see
at0: unvanted interrupt message. Maybe we need flag similar to
SLEEP_HACK on wd driver?
I'm not sure how I'm going to handle this yet, but it is on my TODO
list...
-Søren
To Unsubscribe: send
It seems Doug Rabson wrote:
This seems to be happening to me too on my laptop. The kernel hangs in
ata_command() waiting for an interrupt (ATA_WAIT_INTR) when it is trying
to probe the slave device on my second ide controller. Specifically, it
is the first ata_command() in ata_get_param() which
It seems Doug Rabson wrote:
Are you sure it tries to probe the slave ??
Could please try to have it printout scp-devices in ata_probe ??
Here is a log of an attempted boot with ATA_DEBUG defined. It looks like
ata_probe() detected a slave where there isn't one.
ata1: devices = 0xc
Third update to the new ATA/ATAPI driver:
ZIP drives should now be working, I'm not sure about LS120 drives,
reports on those most welcome!
Fixed problems:
Hang on probe on fantom devices.
The probe now use a timeout to avoid hangs if no interrupt
is received.
There has
It seems Steve Price wrote:
On Sun, 7 Mar 1999, Mike Smith wrote:
#
# From the context I've seen, the 'ufs_dirbad' panic is almost certainly
# due to corrupted disk input.
I definitely can't rule that out as a possibility, but it does make
it difficult to explain how the old driver
It seems Brian Feldman wrote:
Third update to the new ATA/ATAPI driver:
ZIP drives should now be working, I'm not sure about LS120 drives,
reports on those most welcome!
It doesn't lock up like before, but on my LS-120
wdc1: unit 0 (atapi): LS-120 COSM 02 UHD Floppy/0271C09T,
It seems Steve Price wrote:
[debug output omitted]
I think I know what is failing now, I just have to find a fix for it..
-Søren
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Second update to the new ATA/ATAPI driver:
Now all actual probing of both ATA ATAPI devices are done after
interrupts are enabled, this kills the last unwanted interrupts
(and there is no ugly hacks like in the old driver to avoid them).
Command interrupt devices are now supported, this applies
It seems Fritz Heinrichmeyer wrote:
I tried to use the ZIP-disk with the native file format:
when copying something to /mnt,
i see with dmesg
ata0: unwanted interrupt
ata0: unwanted interrupt
atapi_transfer: bad command phase
I think this is fixed in the update I just committed. I
It seems Chan Yiu Wah wrote:
Hi,
I had successfully made the world using egcs-1.1.2pre. However, i encountered
an error when tring to make the kernel. The error is as followings. Anyone
knows how to solve it. Thanks.
Clarence
=== make depend error ===
cc -c -O -Wall
It seems Steve Price wrote:
This works a little better on my machine. It doesn't panic
anymore more. It just hangs where it used to panic. Should
I turn on the DEBUG output, hand scribe the output, and send
it to you?
That would be very helpfull yes...
-Søren
To Unsubscribe: send mail to
It seems Brian Feldman wrote:
After testing out the new ATA drivers, I've only got a single problem. My
box locked up while accessing the LS-120 (and, seemingly, swapping):
Mar 4 00:20:02 green /kernel: atapi_transfer: bad command phase
Mar 4 00:20:33 green /kernel: swap_pager: indefinite
It seems Alex Zepeda wrote:
On Thu, 4 Mar 1999, oZZ!!! wrote:
What exactly is 'unwanted interrupt' supposed to mean, and is it
likely to be a problem in my kernel configuration? (I can send a copy
of it on request...)
i think it tell you about not used 2nd IDE controller...
It seems oZZ!!! wrote:
ad0: FUJITSU MPA3026AT/9147 ATA-3 disk at ata0 as master
ad0: 2503MB (5126964 sectors), 5086 cyls, 16 heads, 63 S/T, 512 B/S
ad0: 16 secs/int, 0 depth queue
ad1: Maxtor 71336 AP/2A3C0B31 ATA-? disk at ata0 as slave
ad1: 1277MB (2616240 sectors), 2595 cyls, 16 heads,
It seems Dan Nelson wrote:
wdc0: unit 0 (wd0): IBM-H2344-A4, multi-block-4, sleep-hack
wd0: 328MB (672525 sectors), 915 cyls, 15 heads, 49 S/T, 512 B/S
ad0 probe output:
ad0: IBM-H2344-A4/G4I_A8C0 ATA-? disk at ata0 as master
ad0: 549280MB (1124925450 sectors), 915 cyls, 15 heads, 49
It seems Mike Zanker wrote:
My kernel is failing at the make depend stage owing to typos in the new
ATA code. It seems that atapi-all.c is trying to include atapifd.h when
the file is actually called atapi-fd.h. The same may apply to other
included files.
No it was because I forgot to add the
It seems Eric Haug wrote:
Hi
I am also seeing this same problem.
With ATA_DEBUG and AD_DEBUG I see that blocks 127 and 2127
are read successfully and then the panic.
Sounds like either it dont get the geometry right, or it uses too
many secs/int for the drive to handle. Anyhow there is a new
It seems Sheldon Hearn wrote:
Guess the answer for now is that people who can't live without
statically numbered drives continue to use the older IDE driver or mail
Soren diffs for adding device wiring support. :-)
Well, well, don't panic :)
I'll provide an option in the next commit round
It seems Bob K wrote:
On Tue, 2 Mar 1999, Lee Cremeans wrote:
Will this new ATA driver finally support DMA correctly on ATAPI devices (as
opposed to pure ATA disk devices)? This is a feature that could really come
in handy for me (as well as a reason to migrate back to -current from 3.1
It seems Tugrul wrote:
I deleted the annoucement email, but looking over LINT, the
following lines seemed appropiate for my 486:
controllerata0at isa? port IO_WD1 bio irq 14
deviceatadisk0
Correct.
First problem I had was that the kernel would not link
First update to the new ATA/ATAPI driver:
Added driver to support ATAPI floppies ie LS-120 ZIP drives.
I'm not too sure of this 2 hour job, I cannot get writeprotect
disabled on the only ZIP medium I just got, but I can read the
disk. Reports are welcome on LS-120 drives too, they are very
hard
It seems Nicolas Souchu wrote:
What would you think of parallel port devices? Would it be easy
to make the new ATAPI stuff work with ppbus? I especially think
about the HP7200 CD-RW which has certainly hard real-time constraints
to burn a CD.
Hmm, you have any docs on how to talk to such a
It seems Geoff Rehmet wrote:
Søren Schmidt writes :
Good work, no more stinky delay :-)
Thanks!, and I hate delays too :)
It works beautifully for me. I can imagine that the people
with UDMA drives can't wait for DMA support in it. :-)
Its in the works, together with the tagged
It seems Geoff Rehmet wrote:
Interesting, what flags did you use with the old driver (wd) ??
Just some results of testing the comparison of wd and ata:
Both bonnie tests were run on a freshly booted machine, P133,
64M RAM, running X and netscape, but only Bonnie active:
It seems Sheldon Hearn wrote:
On Mon, 01 Mar 1999 13:19:20 PST, Søren Schmidt wrote:
# for a PCI only system (most modern machines)
controllerata0
deviceatadisk0# ATA disks
deviceatapicd0# ATAPI CDROM's
device
It seems Sheldon Hearn wrote:
The only thing that bit me was that I used wd0 and wd2 with the older
driver, whereas the newer driver automatically decided to use ad0 and
ad1. This is expected behaviour, but it's something for other weenies
to watch out for. :-)
I warned about that in the
It seems Thomas T. Veldhouse wrote:
Will the new ATAPI drivers still work with wormcontrol for ATAPI CD Writers?
Since it is a WIP, will it support it if it doesn't?
It should, but i just found out that it somehow fails, I'm bughunting...
-Søren
To Unsubscribe: send mail to
It seems Lee Cremeans wrote:
Will this new ATA driver finally support DMA correctly on ATAPI devices (as
opposed to pure ATA disk devices)? This is a feature that could really come
in handy for me (as well as a reason to migrate back to -current from 3.1 :)
Its on my list of wanted items, so
It seems Daniel O'Connor wrote:
On 02-Mar-99 SXren Schmidt wrote:
Its in the works, together with the tagged queuing some of the
newer drives supports.
Wow! :)
Is there any chance od adding the ability to 'wire' devices a la SCSI? :)
I'll think about it, but lots of things has higher
Finally!!
The much roumored replacement for our current IDE/ATA/ATAPI is
materialising in the CVS repositories around the globe.
So what does this bring us:
A new reengineered ATA/ATAPI subsystem, that tries to overcome
most of the deficiencies with the current drivers.
It supports PCI as
It seems oZZ!!! wrote:
controller ata0
device atadisk0# ATA disks
device atapicd0# ATAPI CDROM's
After (fastest(!!!)) boot:
$ dmesg
..
chip1: Intel 82371AB PCI to ISA bridge rev 0x01 on pci0.7.0
ata-pci0: Intel PIIX4 IDE controller rev
It seems David Kelly wrote:
S ren Schmidt writes:
There is NO support for bad144, if your disk is bad, ditch it, it has
already outgrown its internal spare sectors, and is dying.
Speaking of which, is there any portable way to monitor bad block lists
on ATA drives? And the S.M.A.R.T
It seems Brian Feldman wrote:
Do you have any plans to move the wfd(4) driver to the new ATA framework?
I'd
be glad to test it all out, as long as I don't lose my LS-120's functionality.
Thanks in advance!
I'm, waiting for my ZIP drive to arrive, then there will be an atapi-fd
driver as
It seems Tugrul wrote:
The new driver fails to build when devfs is also in the config. I
made a simple change of static void *devfs_token to void *devfs_token
on line 183 in ata-all.h and all seems good.
I know, I was thi close to ripping all the devfs stuff out, but...
Good
It seems Daniel C. Sobral wrote:
On the code:
ireason = inb (ata-port + AR_IREASON);
ac-result.status = inb (ata-port + AR_STATUS);
phase = (ireason (ARI_CMD | ARI_IN)) |
- (ac-result.status ARS_DRQ);
It seems Daniel C. Sobral wrote:
Søren Schmidt wrote:
The problem is the ARS_BSY signal. If my memory doesn't fail me, if
ARS_BSY is active, then the other signals may contain trash. In this
particular loop, ARS_BSY could be active, but it wasn't being
checked for, on the
It seems Mike Tancsa wrote:
On 24 Feb 1999 18:39:36 -0500, in sentex.lists.freebsd.current you wrote:
Hmm, which suggests that I need to leave the do it by hand code in
there and recommend removing the BIOS :(
Are there any plans to support the Promise Fast Trak IDE RAID controller ?
It seems Martin Cracauer wrote:
In 199902230725.caa02...@y.dyson.net, John S. Dyson wrote:
Søren Schmidt said:
It should work, but the promise support in the old system is, well,
hacky at best. I'm not sure if Promise supports more than one card
at a time, but from looking at the
It seems John S. Dyson wrote:
Søren Schmidt said:
It should work, but the promise support in the old system is, well,
hacky at best. I'm not sure if Promise supports more than one card
at a time, but from looking at the chip specs, it should work just
fine, and if the hardware works,
It seems Manuel Bouyer wrote:
Hi,
I initially intended to ask this to John Dyson, but I don't know how
to reach him. Maybe someone else on this list can anserw :)
I'm looking for documentations about the promise PCI IDE controller,
to add support for this in NetBSD. Does someone know how John
It seems Andrew Gallatin wrote:
Søren Schmidt writes:
If you have questions, I might be able to answer, having just written
the support for our new ata/atapi system
Is this new ata/atapi system the rumored rewrite of the existing IDE
(i386/isa/wd.c, /pci/ide_pci.c) driver?
It seems Kenneth D. Merry wrote:
Gary Jennejohn wrote...
Are there any plans to add devstat support to atapi-cd.c, a la scsi_cd.c ?
Is it even considered to be desirable ?
I think it is desireable. I think the best person to do it is probably
Soren or someone else who is familar with
It seems Poul-Henning Kamp wrote:
Is wd0: DMA failure, DMA status 0 something which needs looked at ?
Blame Julian, he broke it in v 1.183 of wd.c, the following patch
works on all my HW, but I dont have the cyrix chipset Julian
made the patch for, to test it on (it also contains other small
It seems Tommy Hallgren wrote:
Hi!
Now that the console system is restructured, shouldn't we consider
using GGI instead of inventing the wheel?
I happened to find this link and they seem to be positive to
supporting FreeBSD.
http://synergy.caltech.edu/~ggi/mailinglist/ev-mar98/139.html
It seems Karl Pielorz wrote:
This is due to Julians commit in 1.183 (IIRC) of wd.c, its bogus :(
The following patchh cures the mess, and fixes a couble of other
nits as well:
-Søren
Index: wd.c
===
RCS file:
It seems David Dawes wrote:
I've been playing with a Promise FastTrack RAID (IDE) controller with
3.0-current as of yesterday. Although it is recognised in the PCI bus
probe as a Promise Ultra/33 (it has the same vendor/chip ID as the
non-RAID card), the probes in i386/isa/wd.c fail. I added
It seems David Dawes wrote:
That didn't improve things, but with the patch I got lots of messages
like the following (for a disk attached to the onboard PIIX4):
wd1: DMA failure, DMA status 0
(The box isn't SMP.)
Hmm, and it is an uptodate -current system ??
Just use this part then:
It seems David Dawes wrote:
I also run the card without its BIOS, as that tends to get in the way.
I think the FastTrack is just an Ultra/33 with another BIOS chip on it.
I'll try pulling the BIOS tomorrow. We didn't get this card for it's
RAID features anyway.
That helped me in a
It seems Jordan K. Hubbard wrote:
Also, I suspect having acd in the kernel and wcd in MAKEDEV may
lead to confusion for some people.
I was under the impression that Soren was going to rename acd to wcd
before the branch.
Oops, forgot about that one...
In fact I was going to add BOTH
66 matches
Mail list logo
