In message [EMAIL PROTECTED], Luoqi Chen writes:
This discussion is not going anywhere. Why can't everyone calm down and
find a comprise? Here's my proposal:
1. leave the the code and config option in the source tree for now
2. remove all traces of wd in documentation/GENERIC/LINT/MAKEDEV
that
I think there has been enough objections to the idea of just removing wd.c
for it to stay for a few months.
It doesn't hurt to keep it. Especially if it's not on by default.
I think this argument can go away for a while.
On Fri, 10 Dec 1999, Poul-Henning Kamp wrote:
In message [EMAIL
At 3:05 PM -0700 1999/12/10, Kenneth D. Merry wrote:
I agree that the CAM integration shouldn't be used as a precedent here. I
don't agree with your characterization of it as a "debacle", though.
On the whole, we gained a whole lot and lost very little.
Long-term, yes I believe
At 11:22 PM 12/10/99 +0100, Poul-Henning Kamp wrote:
This discussion is not going anywhere. Why can't everyone calm down and
find a comprise? Here's my proposal:
1. leave the the code and config option in the source tree for now
2. remove all traces of wd in
On Fri, 10 Dec 1999, Poul-Henning Kamp wrote:
Listen guys, this is a tempest in a tea-cup, we are not loosing any
functionality here, we are gaining functionality.
Poul-Henning, what I'm seeing here is a LOT of voices raised against this
idea, both from key developers and other citizens of
Brad Knowles wrote...
At 3:05 PM -0700 1999/12/10, Kenneth D. Merry wrote:
I agree that the CAM integration shouldn't be used as a precedent here. I
don't agree with your characterization of it as a "debacle", though.
On the whole, we gained a whole lot and lost very little.
On Fri, 10 Dec 1999, Poul-Henning Kamp wrote:
This fails the most important criteria for the transistion to ATA:
it doesn't break existing kernel configs.
Listen guys, this is a tempest in a tea-cup, we are not loosing any
functionality here, we are gaining functionality.
The wd
In message [EMAIL PROTECTED], Kris Ken
naway writes:
No-one (as far as I can see) is objecting to making ata the default (which
it already is), and to kill wd in some number of weeks. Why can't you just
do that, and put and end to this discussion happily? Will a few weeks
really harm the
Poul-Henning Kamp [EMAIL PROTECTED] wrote:
Once we have established that the new driver doesn't leave a large
number of people stranded it will be killed for good.
I think this is a key issue, if not *THE* key issue.
Please correct me if I'm wrong, but PHK and others are basically
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: You overlook one simple thing here: If we want the ata driver tested,
: we need to make existing kernel configs break, otherwise people
: will not change them to use ata. We know this from bitter experience.
If all you are talking about
If half as much energy was spent adding the missing bits of functionality
to the new systems as people have been spending complaining it then we'd be
there ages ago.
Not true. It doesn't take a disk expert to complain about a policy, but
it takes one to fix bugs/add features to the
On Friday, 10th December 1999, "Kenneth D. Merry" wrote:
Brad Knowles wrote...
At 3:05 PM -0700 1999/12/10, Kenneth D. Merry wrote:
I agree that the CAM integration shouldn't be used as a precedent here.
I don't agree with your characterization of it as a "debacle", though.
On the
We've been telling people for a long time that the wd driver would
remain around even after ata went golden to support the ESDI systems
still in service. That sounds like it is changing now.
Real support for ESDI died with bad144... Error free ESDI disks are
very rare, even the best in my
Stephen McKay wrote...
On Friday, 10th December 1999, "Kenneth D. Merry" wrote:
Brad Knowles wrote...
At 3:05 PM -0700 1999/12/10, Kenneth D. Merry wrote:
I agree that the CAM integration shouldn't be used as a precedent here.
I don't agree with your characterization of it as a
On Fri, 10 Dec 1999, Kenneth D. Merry wrote:
And as for the device renaming, you didn't have to change anything from
sd-da. The old device names and nodes were supported in most every way.
There were a lot of mis-informed people on the lists who claimed that you
had to change your device
And as for the device renaming, you didn't have to change anything from
sd-da. The old device names and nodes were supported in most every way.
There were a lot of mis-informed people on the lists who claimed that you
had to change your device names. That was completely untrue, and I
On Friday, 10th December 1999, Mike Smith wrote:
The same mentality that made the CAM cutover a "debacle" is making the
ata cutover a "debacle".
This "mentality" might be an unavoidable part of human nature. I found
That was my musing in the next paragraph.
my first reaction was
The same thing is about to apply to the woxware sound code, we have a
new shiny system that works and is much better designed...
Actually, I'm sad to say that our shiny new sound system does *not*
work for some of the most popular audio chipsets on the market today
(where the older "luigi"
Mike Smith wrote...
And as for the device renaming, you didn't have to change anything from
sd-da. The old device names and nodes were supported in most every way.
There were a lot of mis-informed people on the lists who claimed that you
had to change your device names. That was
The ATA driver went golden now, and to make sure nobody is distracted
from testing it before 4.0-RELEASE is cut, the wd driver will be
removed.
It's really that simple.
Well, I'm not sure that's really true yet and I would honestly prefer
it if you wouldn't make "conclusive statements"
Except that ATA currently does not work on my system. So I assume I'm not
the only one.
Actually, to quote from your original message:
] According to technical product summary, the primary IDE interface, on
] which both my drives reside, is a PCTech RZ1000 on the PCI local bus.
Nobody in
In message [EMAIL PROTECTED], Warner Losh writes:
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: You overlook one simple thing here: If we want the ata driver tested,
: we need to make existing kernel configs break, otherwise people
: will not change them to use ata. We know this from
It seems Blaz Zupan wrote:
On Wed, 8 Dec 1999, Christopher Masto wrote:
I fully agree that these things are neccessary and good. I just think
we need avoid jumping the gun on removing the old code, when some
people still need it to boot their machines.
Actually I completely disagree.
Julian Elischer wrote:
please do not remove it..
just make it non-default.
Retire it to LINT if you must, but I'd also like to see it around
until the last release on RELENG_3.
--
Daniel C. Sobral(8-DCS)
who is as social as a wampas
[EMAIL PROTECTED]
[EMAIL
On 8 Dec, Soren Schmidt wrote:
Søren: I didn´t want to flame you, I only want to convince Paul-Henning
to wait until you have time to fix those bugs.
Welcome to the real world, I've promised to look at this and I will,
but a day has only so many hours.
I asumed this, and because of this
In message [EMAIL PROTECTED] Julian
Elischer writes:
: more importantly we lost the aha driver for a while.
No we didn't. Well, the aha driver did loose support for the 1542A
cards, but the aha driver was done so that cam could be committed to
the tree. Maybe you are confusing things
In message [EMAIL PROTECTED] Christopher Masto writes:
: Right now, I have no sound (not detected), no USB (panic on removal),
: can't use my sio pccard, can't eject my ed pccard, my IDE drives are
: taking hours to dump and fsck, and my TV card is missing every other
: line if I try to use
On Wednesday, 8 December 1999 at 21:00:36 +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Kris Ken
naway writes:
On Wed, 8 Dec 1999, Poul-Henning Kamp wrote:
Update your /etc/fstab (use /dev/ad* instead of /dev/wd* or
/dev/rwd*
Can't we keep the same device
On Wednesday, 8 December 1999 at 20:23:24 +0100, Brad Knowles wrote:
At 10:56 AM -0800 1999/12/8, Mike Smith wrote:
The right attitude to be taking now is "here is where the ata drivers
still fall down" or "here are patches to them to replace this
functionality". Think about the
On Wednesday, 8 December 1999 at 12:52:37 -0800, Mike Smith wrote:
On Wed, Dec 08, 1999 at 10:56:24AM -0800, Mike Smith wrote:
You shouldn't remove a function until it has been properly replaced.
A very simple concept some people seem to have trouble grasping.
Actually, that's not at all
On Wednesday, 8 December 1999 at 15:23:49 -0800, Jonathan M. Bresler wrote:
[snip]
We gained quite a bit from it, but let's not rewrite history. I
remember quite clearly that there was a very popular Adaptec SCSI
controller missing when the switch to CAM was made, and a lot of
[snip]
On Wednesday, 8 December 1999 at 17:09:39 +0100, Soren Schmidt wrote:
It seems Alexander Leidinger wrote:
It isn´t only a matter of providing feedback... the maintainer also has
to work on it.
Yeah, right...
I offered feedback in every mail regarding my problem with ata
msdos-ZIPs
On Wednesday, 8 December 1999 at 22:31:22 +0100, Soren Schmidt wrote:
It seems Christopher Masto wrote:
On Wed, Dec 08, 1999 at 10:56:24AM -0800, Mike Smith wrote:
You shouldn't remove a function until it has been properly replaced.
A very simple concept some people seem to have trouble
On Wednesday, 8 December 1999 at 15:02:37 +0100, Soren Schmidt wrote:
It seems Richard Seaman, Jr. wrote:
On Wed, Dec 08, 1999 at 12:55:35PM +0100, Poul-Henning Kamp wrote:
In a few days time the wd driver will be retired from FreeBSDs
i386 architecture.
Since the ata driver does not
Zitiere Daniel Eischen [EMAIL PROTECTED]:
In message [EMAIL PROTECTED]
Christopher Masto
writes:
: Right now, I have no sound (not detected), no USB
(panic on removal),
: can\\\'t use my sio pccard, can\\\'t
eject my ed
pccard, my IDE drives are
: taking
On 9 Dec, Maxim Sobolev wrote:
Excuse me for possible off-topic, but I have what is seems for me fresh idea
about this question. Why do not remove from wd driver support for chipsets
already implemented/tested in ata driver? Thus both clans would satisfied
i.e. users with unsupported by ata
It seems Greg Lehey wrote:
OK, you asked for it, following is a patch to support the
sis 5591 chipset. Remember this is done blindfolded, I
have no HW to test on, but you guys do :)
Let me know what happens...
OK. Let's defer removing wd until we know that ata DMA works on these
In message [EMAIL PROTECTED], Greg Lehey writes:
The fallback path is not eliminated, and may never be, but it may become
rather uncomfortable to linger on it longer than you absolutely need to.
Would you care to expand on that statement?
Apart from the fsck/root/reload issue (for which
Alexander Leidinger wrote:
On 9 Dec, Maxim Sobolev wrote:
Excuse me for possible off-topic, but I have what is seems for me fresh idea
about this question. Why do not remove from wd driver support for chipsets
already implemented/tested in ata driver? Thus both clans would satisfied
On Thu, Dec 09, 1999 at 04:03:58PM +0100, Soren Schmidt wrote:
It seems Greg Lehey wrote:
OK, you asked for it, following is a patch to support the
sis 5591 chipset. Remember this is done blindfolded, I
have no HW to test on, but you guys do :)
Let me know what happens...
OK.
It seems Maxim Sobolev wrote:
There also exist cases where the chipset is supported but a particular
functionality isn_t supported yet (in my case it_s the possibility to
access MS-DOS formated ZIP-disks, harddisk access works well, and I_m
not the only one with this problem (not counting
It seems Richard Seaman Jr. wrote:
It already being tested, and it works, but at the same tike I found
out that the code in the old driver for the sis is schizofrenic, it
has one way of setting things up, and another way of reporting how
it is set :(, that way it is difficult to
It seems Greg Lehey wrote:
I think the old wd code was broken on reporting. The reporting
was changed from the original submission, when it was committed.
Yep, but it does mean that people _belive_ they are running UDMA
where in fact they aren't, and now they blaim the ata driver
[snip]
Again, this is not accurate. I have a laptop with which, two months
ago, I could use my LinkSys ethernet card, and I could use my digital
then we need to get your LinkSys ethernet card support fixed.
i am using one to write this message. mine is a LinkSys 10/100 PCMCIA
What version of -CURRENT are you using? Mine is a PCMPC200, and I
haven't been able to get it to work for 6 weeks.
PCMPC100 LinkSys PCMCIA 10/100
jmb
Greg, yours is a card bus card. it is not supported at this
time. i have one right next to me with the label melted.
In message [EMAIL PROTECTED] Brian Somers writes:
: The aha driver broke somewhere between the 5th and 8th of this month.
: Boot -v says ``aha0: status reg test failed ff''.
Odd.. What kind of card do you have?
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
In message [EMAIL PROTECTED] Wilko Bulte writes:
: Not quite true: the esp driver for the alphas got lost. No attack on anyone,
: just stating a fact.
As did the sea and uha drivers. I had a fantacy that I'd have time to
write one. However, I didn't... :-(
Warner
To Unsubscribe: send mail
In message [EMAIL PROTECTED] Thomas David Rivers writes:
: I lost support on my 1542B until I came up with a patch, which
: I believe was incorporated into 3.3-R.
Yes. I stand corrected. The B that I had worked w/o the patch, but
many B's in the field didn't :-(.
Warner
To Unsubscribe:
-On [19991209 06:59], Warner Losh ([EMAIL PROTECTED]) wrote:
: P.S. I'm not trying to cut down Warner, but I do think we really need to
: focus on regaining support for things we've lost in the past 6 months.
I agree with this completely. The newbus excursion of the old code
likely was a big
-On [19991209 12:00], Wilko Bulte ([EMAIL PROTECTED]) wrote:
As Mike Smith wrote ...
On Wed, Dec 08, 1999 at 10:56:24AM -0800, Mike Smith wrote:
[there] were the SCSI drivers lost to CAM
Actually, most of this is histrionics. CAM didn't lose us SCSI drivers;
Not quite true: the esp
-On [19991209 16:03], Greg Lehey ([EMAIL PROTECTED]) wrote:
On Wednesday, 8 December 1999 at 20:23:24 +0100, Brad Knowles wrote:
This is -CURRENT. It pains me to say it, but anyone trying to
run anything "useful" on -CURRENT gets what they deserve. This is
the only place where we can
-On [19991209 00:03], Bill Fumerola ([EMAIL PROTECTED]) wrote:
On Wed, 8 Dec 1999, Soren Schmidt wrote:
The same thing is about to apply to the woxware sound code, we have a
new shiny system that works and is much better designed...
For some definitions of "works".
Low shot. If not for
On Thu, 9 Dec 1999, Jeroen Ruigrok/Asmodai wrote:
For some definitions of "works".
Low shot. If not for Cameron and Sanimura-san we would still be left
dangling with the hopeless kludge of pcm vs VoxWare. They finally put
their effort into something which all questions plus remarks on
On 9 Dec, Maxim Sobolev wrote:
Excuse me for possible off-topic, but I have what is seems for me fresh idea
about this question. Why do not remove from wd driver support for chipsets
already implemented/tested in ata driver? Thus both clans would satisfied
i.e. users with unsupported
I'm completely at a loss as to how the ata driver could be responsible
for your inability to read these disks. I don't have a copy of your
original problem report to hand, but since I have all the hardware here
I'd appreciate it if you could be a little more explicit about your
As Jeroen Ruigrok/Asmodai wrote ...
-On [19991209 12:00], Wilko Bulte ([EMAIL PROTECTED]) wrote:
As Mike Smith wrote ...
On Wed, Dec 08, 1999 at 10:56:24AM -0800, Mike Smith wrote:
[there] were the SCSI drivers lost to CAM
Actually, most of this is histrionics. CAM didn't lose us
As Warner Losh wrote ...
In message [EMAIL PROTECTED] Brian Somers writes:
: The aha driver broke somewhere between the 5th and 8th of this month.
: Boot -v says ``aha0: status reg test failed ff''.
Odd.. What kind of card do you have?
Does it make a difference if you run boot without -v
In message [EMAIL PROTECTED] Brian Somers writes:
: The aha driver broke somewhere between the 5th and 8th of this month.
: Boot -v says ``aha0: status reg test failed ff''.
Odd.. What kind of card do you have?
aha0 at port 0x330-0x333 irq 11 drq 7 on isa0
aha0: AHA-1542CP FW Rev. D.0
As Warner Losh wrote ...
In message [EMAIL PROTECTED] Brian Somers writes:
: The aha driver broke somewhere between the 5th and 8th of this month.
: Boot -v says ``aha0: status reg test failed ff''.
Odd.. What kind of card do you have?
Does it make a difference if you run boot
On Wed, 8 Dec 1999, Soren Schmidt wrote:
It seems Julian Elischer wrote:
please do not remove it..
And why is that ?? There is no point in having done a new one then, and
you guys have known I've been working on this for ages so this cannot
come as a surprise to anybody...
The same
In a few days time the wd driver will be retired from FreeBSDs
i386 architecture.
Users, please:
Update your kernel config file (see GENERIC)
Update your /etc/fstab (use /dev/ad* instead of /dev/wd* or
/dev/rwd*
Copy MAKEDEV from src/etc/MAKEDEV to
On Wed, Dec 08, 1999 at 12:55:35PM +0100, Poul-Henning Kamp wrote:
In a few days time the wd driver will be retired from FreeBSDs
i386 architecture.
Since the ata driver does not support DMA on my chipset, at
least the last time I tried (SiS 5591), it would be nice
to leave the wd driver
On Wed, 08 Dec 1999 12:55:35 +0100, Poul-Henning Kamp wrote:
In a few days time the wd driver will be retired from FreeBSDs
i386 architecture.
I know there are issues that make it awkward to support both drivers,
but it's probably a good idea to keep the wd driver available for those
who
On Wed, Dec 08, 1999 at 07:27:28AM -0600, "Richard Seaman, Jr." [EMAIL PROTECTED] wrote:
In a few days time the wd driver will be retired from FreeBSDs
i386 architecture.
Since the ata driver does not support DMA on my chipset, at
least the last time I tried (SiS 5591), it would be nice
It seems Richard Seaman, Jr. wrote:
On Wed, Dec 08, 1999 at 12:55:35PM +0100, Poul-Henning Kamp wrote:
In a few days time the wd driver will be retired from FreeBSDs
i386 architecture.
Since the ata driver does not support DMA on my chipset, at
least the last time I tried (SiS
On 8 Dec, Sheldon Hearn wrote:
In a few days time the wd driver will be retired from FreeBSDs
i386 architecture.
I know there are issues that make it awkward to support both drivers,
but it's probably a good idea to keep the wd driver available for those
who need it, even if it requires
It seems Alexander Leidinger wrote:
It isn´t only a matter of providing feedback... the maintainer also has
to work on it.
Yeah, right...
I offered feedback in every mail regarding my problem with ata
msdos-ZIPs (they aren´t accessible), but most of the time I havn´t got a
reply (Søren
please do not remove it..
just make it non-default.
On Wed, 8 Dec 1999, Poul-Henning Kamp wrote:
In a few days time the wd driver will be retired from FreeBSDs
i386 architecture.
Users, please:
Update your kernel config file (see GENERIC)
Update your /etc/fstab (use
while you're about it the cyrix GXM?
On Wed, 8 Dec 1999, Soren Schmidt wrote:
It seems Richard Seaman, Jr. wrote:
On Wed, Dec 08, 1999 at 12:55:35PM +0100, Poul-Henning Kamp wrote:
In a few days time the wd driver will be retired from FreeBSDs
i386 architecture.
Since the
because it doesn't support the chipsets that the old one does.
(namely the 200 or so lines of support in pci_ide.c needed for the Cyrix
GXM series).
You shouldn't remove a function until it has been properly replaced.
A very simple concept some people seem to have trouble grasping.
On Wed, 8
there is plenty of code in the original
that does ALL you need, and I can test it.
On Wed, 8 Dec 1999, Soren Schmidt wrote:
It seems Julian Elischer wrote:
while you're about it the cyrix GXM?
Docs? HW? tester? in that order
-Søren
To Unsubscribe: send mail to [EMAIL
because it doesn't support the chipsets that the old one does.
(namely the 200 or so lines of support in pci_ide.c needed for the Cyrix
GXM series).
You shouldn't remove a function until it has been properly replaced.
A very simple concept some people seem to have trouble grasping.
On Wed, 8 Dec 1999, Poul-Henning Kamp wrote:
Update your /etc/fstab (use /dev/ad* instead of /dev/wd* or
/dev/rwd*
Can't we keep the same device names? I thought that was the original plan
way back when, once the new driver was ready for prime-time.
Also, perhaps we
PROTECTED]
To: Julian Elischer [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, December 08, 1999 1:56 PM
Subject: Re: HEADSUP: wd driver will be retired!
because it doesn't support the chipsets that the old one does.
(namely the 200 or so lines of support in pci_ide.c needed
In message [EMAIL PROTECTED], Jul
ian Elischer writes:
Someone replacing a module and deleting th eoriginal should make a decent
effort to cover all the present functionality. (OR make a decision that
such functionality will never be covered, (e.g. bad144)).
Just breaking things because you felt
On Wed, Dec 08, 1999 at 10:56:24AM -0800, Mike Smith wrote:
You shouldn't remove a function until it has been properly replaced.
A very simple concept some people seem to have trouble grasping.
Actually, that's not at all correct. We've demonstrated a number of
times now that you reach
On Wed, Dec 08, 1999 at 10:56:24AM -0800, Mike Smith wrote:
You shouldn't remove a function until it has been properly replaced.
A very simple concept some people seem to have trouble grasping.
Actually, that's not at all correct. We've demonstrated a number of
times now that you
On Wed, 8 Dec 1999, Soren Schmidt wrote:
The same thing is about to apply to the woxware sound code, we have a
new shiny system that works and is much better designed...
For some definitions of "works".
--
- bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp -
- ph:(800)
On Wed, Dec 08, 1999 at 10:31:22PM +0100, Soren Schmidt wrote:
Hmm, well, if you want support for any of the new ata-66 controllers
you have to use the ata driver, so you loose some you win some.
Given that my patch for the SiS works and a patch I got from Luoqi,
the ONLY support you are
On Wed, Dec 08, 1999 at 12:52:37PM -0800, Mike Smith wrote:
Unfortunately, FreeBSD has far too many examples of a working system
being replaced with a less functional system. Just off the top of my
head, there were the SCSI drivers lost to CAM, the PCCARD system,
sound drivers, and now
On Wed, Dec 08, 1999 at 12:52:37PM -0800, Mike Smith wrote:
We haven't "lost" the pccard system at all
I've lost the ability to use a 3c574 10/100 card (panics), the Xircom
`xe' card (will not attach), the `ep' driver now has ultra shitty
performance (132.05 KB/sec) where it seems to only be
[snip]
We gained quite a bit from it, but let's not rewrite history. I
remember quite clearly that there was a very popular Adaptec SCSI
controller missing when the switch to CAM was made, and a lot of
[snip]
we lost teh aic controller at that time.
[snip]
Again, this is
On Wed, 8 Dec 1999, Jonathan M. Bresler wrote:
[snip]
We gained quite a bit from it, but let's not rewrite history. I
remember quite clearly that there was a very popular Adaptec SCSI
controller missing when the switch to CAM was made, and a lot of
[snip]
more importantly
Julian Elischer wrote...
On Wed, 8 Dec 1999, Jonathan M. Bresler wrote:
[snip]
We gained quite a bit from it, but let's not rewrite history. I
remember quite clearly that there was a very popular Adaptec SCSI
controller missing when the switch to CAM was made, and a lot of
On Wed, 8 Dec 1999, Jonathan M. Bresler wrote:
[snip]
We gained quite a bit from it, but let's not rewrite history. I
remember quite clearly that there was a very popular Adaptec SCSI
controller missing when the switch to CAM was made, and a lot of
[snip]
more
On Wed, Dec 08, 1999 at 03:02:37PM +0100, Soren Schmidt wrote:
OK, you asked for it, following is a patch to support the
sis 5591 chipset. Remember this is done blindfolded, I
have no HW to test on, but you guys do :)
Seems to work. I'll let it run for a few days, but I'd guess it
is
On Wed, 8 Dec 1999, David O'Brien wrote:
I've lost the ability to use a 3c574 10/100 card (panics), the Xircom
`xe' card (will not attach), the `ep' driver now has ultra shitty
performance (132.05 KB/sec) where it seems to only be working due to the
watch dog timer.
I'll take the blame for
On Wed, 8 Dec 1999, Christopher Masto wrote:
I fully agree that these things are neccessary and good. I just think
we need avoid jumping the gun on removing the old code, when some
people still need it to boot their machines.
Actually I completely disagree. When you leave in old code in the
In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: In a few days time the wd driver will be retired from FreeBSDs
: i386 architecture.
Isn't this a bit premature? It was my understanding that it would
live through the 4.x release and then die. The ata driver was just
made the default a
In message [EMAIL PROTECTED] Mike Smith writes:
: This is a good time for this particular cutover. A little more public
: announcement would perhaps have been nice, but that's probably asking
: more of our axe-wielding friends than we're ever going to get.
I'd agree more with this if the ata
In message [EMAIL PROTECTED] Christopher Masto writes:
: Right now, I have no sound (not detected), no USB (panic on removal),
: can't use my sio pccard, can't eject my ed pccard, my IDE drives are
: taking hours to dump and fsck, and my TV card is missing every other
: line if I try to use the
: P.S. I'm not trying to cut down Warner, but I do think we really need to
: focus on regaining support for things we've lost in the past 6 months.
I agree with this completely. The newbus excursion of the old code
likely was a big mistake. We have a basically working system now, but
I've not
In message [EMAIL PROTECTED] Julian
Elischer writes:
: more importantly we lost the aha driver for a while.
No we didn't. Well, the aha driver did loose support for the 1542A
cards, but the aha driver was done so that cam could be committed to
the tree. Maybe you are confusing things with the
On Wed, Dec 08, 1999 at 10:52:42PM -0700, Warner Losh wrote:
In message [EMAIL PROTECTED] Christopher Masto writes:
: Right now, I have no sound (not detected), no USB (panic on removal),
: can't use my sio pccard, can't eject my ed pccard, my IDE drives are
: taking hours to dump and fsck,
: still alive on Sunday, I'll be able to confirm whether the problem
: is still present and if so, try to fix it.
That would be great!
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
In message [EMAIL PROTECTED] Julian
Elischer writes:
: more importantly we lost the aha driver for a while.
No we didn't. Well, the aha driver did loose support for the 1542A
cards, but the aha driver was done so that cam could be committed to
the tree. Maybe you are confusing things
As Mike Smith wrote ...
On Wed, Dec 08, 1999 at 10:56:24AM -0800, Mike Smith wrote:
Unfortunately, FreeBSD has far too many examples of a working system
being replaced with a less functional system. Just off the top of my
head, there were the SCSI drivers lost to CAM, the PCCARD system,
It seems Richard Seaman, Jr. wrote:
On Wed, Dec 08, 1999 at 03:02:37PM +0100, Soren Schmidt wrote:
OK, you asked for it, following is a patch to support the
sis 5591 chipset. Remember this is done blindfolded, I
have no HW to test on, but you guys do :)
Seems to work. I'll let it
On Thu, 9 Dec 1999, Brian Somers wrote:
The aha driver broke somewhere between the 5th and 8th of this month.
Boot -v says ``aha0: status reg test failed ff''.
Are you sure? I don't see any changes to the driver during this month.
aha.c:
1.33 date: 1999/10/25 04:28:53; author: imp; state:
101 - 199 of 199 matches
Mail list logo
