After Joerg's late-June round of brea^H^H^H^Hcommits to the floppy
driver, I can no longer use my floppy drive. Any attempt to access
the drive (with a known-good writeable floppy in it) simply hangs in
physst state until I eject the disk, at which point it fails with a
hard read error with No
On 6 Jul, David Wolfskill wrote:
As N.Dudorov ([EMAIL PROTECTED]) pointed out, what is happening is that
the sysctl -a in /etc/rc (as part of the entropy harvesting) is failing
to terminate. Whether with GENERIC or LAPTOP_30W, the last entry shown
from sysctl -a is
subscribe freebsd-current
subscribe cvs-all
end
Best regards,
Jack L. Stone,
Administrator
Sage American
http://www.sage-american.com
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Fri, Jul 06, 2001 at 03:08:04PM +1000, Peter Jeremy wrote:
i386 type Alpha type
clock_t unsigned long int
We could make these the same (not sure why they aren't).
ptrdiff_t int long
size_tunsigned intunsigned long
ssize_t
On Fri, Jul 06, 2001 at 04:37:43PM +1000, Peter Jeremy wrote:
On i386, 'gcc -fsyntax-only -Wall x.c' produces no error. On
NetBSD/alpha (same compiler, really), this produces:
x.c: In function `func':
x.c:4: warning: cast from pointer to integer of different size
It'd be *really* nice if
On Fri, Jul 06, 2001 at 07:40:59AM -0700, Mark Peek wrote:
I had the same idea last night. I modified my PowerPC cross-compiler
port to produce an Alpha version. This is based on the lang/gcc295
port so it contains the FreeBSD patches for things like -Wformat. For
sake of example, I only
On Sat, 7 Jul 2001, David O'Brien wrote:
On Fri, Jul 06, 2001 at 03:08:04PM +1000, Peter Jeremy wrote:
i386 type Alpha type
clock_t unsigned long int
We could make these the same (not sure why they aren't).
because on alpha long == 64 bits
ptrdiff_t
On Fri, Jul 06, 2001 at 11:52:05PM +0100, j mckitrick wrote:
I get version 1.15. When I look at the .c,v file in the cvs tree, it says
HEAD is 1.16, but $Id says it is 1.15.
We don't use $Id$ anymore. Do you mean $FreeBSD$? If so, please try
to be more exact. Also try ``cvs status'' on the
On Sat, Jul 07, 2001 at 11:54:26AM -0700, Matthew Jacob wrote:
On Sat, 7 Jul 2001, David O'Brien wrote:
On Fri, Jul 06, 2001 at 03:08:04PM +1000, Peter Jeremy wrote:
i386 type Alpha type
clock_t unsigned long int
We could make these the same (not
On Sat, 7 Jul 2001, David O'Brien wrote:
On Sat, Jul 07, 2001 at 11:54:26AM -0700, Matthew Jacob wrote:
On Sat, 7 Jul 2001, David O'Brien wrote:
On Fri, Jul 06, 2001 at 03:08:04PM +1000, Peter Jeremy wrote:
i386 type Alpha type
clock_t unsigned long
On Sat, Jul 07, 2001 at 01:02:28PM -0700, Matthew Jacob wrote:
On Sat, 7 Jul 2001, David O'Brien wrote:
On Sat, Jul 07, 2001 at 11:54:26AM -0700, Matthew Jacob wrote:
On Sat, 7 Jul 2001, David O'Brien wrote:
On Fri, Jul 06, 2001 at 03:08:04PM +1000, Peter Jeremy wrote:
I don't know what clock_t is used for (kernel version of time_t?).
But the general agreement was to leave time as a 32-bit value on the
Alpha in order to match (1) FreeBSD/i386 and (2) OSF/1,Digital Unix,Tru64.
okay, okay, end the thread...
To Unsubscribe: send mail to [EMAIL PROTECTED]
On Sat, Jul 07, 2001 at 12:00:19PM -0700, David O'Brien wrote:
| On Fri, Jul 06, 2001 at 11:52:05PM +0100, j mckitrick wrote:
| I get version 1.15. When I look at the .c,v file in the cvs tree, it says
| HEAD is 1.16, but $Id says it is 1.15.
|
| We don't use $Id$ anymore. Do you mean
j mckitrick [EMAIL PROTECTED] writes:
On Sat, Jul 07, 2001 at 12:00:19PM -0700, David O'Brien wrote:
| On Fri, Jul 06, 2001 at 11:52:05PM +0100, j mckitrick wrote:
| I get version 1.15. When I look at the .c,v file in the cvs tree, it says
| HEAD is 1.16, but $Id says it is 1.15.
|
| We
Hi
when upgrading a machine from FreeBSD 4.1 to
-current I encountered some problems and I could only solve the first
one:
1. defines HALT, PDWN, PASTE were missing in kbio.h
(defined them)
2. when linking miniperl in stage 3 the function
'setproctitle' was missing
3. eelf_i386.o:
On Fri, Jul 06, 2001 at 06:59:27PM +0200, Dag-Erling Smorgrav wrote:
David O'Brien [EMAIL PROTECTED] writes:
People are making more and more mistakes that break the Alpha build.
We will soon have two more arches.
...which won't really make much difference, as 99% of the difference
in
now that we've removed block devices, there must be a hack
to allow us to read block devices from vmware.
can someone tell me what it is?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Sat, Jul 07, 2001 at 04:42:49PM -0500, Alfred Perlstein wrote:
I'm going to be giving this code some testing, not that you have to
wait for me to finish, but it seems like no one has stepped forward
to review this. I'd like to see it committed, so either go ahead
or wait for my review if
I've committed another round of ACPI changes to -current.
The major addition is CPU throttling support. This is implemented using
ACPI, not any vendor-specific technology, so it should work on any
platform that exports the relevant information. By default, the CPU will
run at 100%
On Thu, Jul 05, 2001 at 07:13:20PM -0700, Kris Kennaway wrote:
Yes, people need to be more careful when enabling WARNS and not do it
until they've positively tested it on alpha.
OR build a 64-bit long (LP64) x86 gcc and test compile with that also.
BDE found *lots* of 64-bit dirty code using
sos Well, sortof, the ata driver doesn't allow for sharing irq1415
sos since lots of boards doesn't work that way. However if you need
sos it you can try to add the shared flag in the driver and see if
sos it works on yours. Hmm, maybe I should make this tunable...
It this patch OK? I've
Daniel Eischen wrote:
On Fri, 6 Jul 2001, Peter Wemm wrote:
Julian Elischer wrote:
On Fri, 6 Jul 2001, Daniel Eischen wrote:
-proc-
-thrgrp-
-thr-
-thrctx-
interesting, though the thrctx maps most closely to a userland thread.
there may be many
Warner Losh wrote:
In message [EMAIL PROTECTED] Mike Smith writes:
:
: sos Well, sortof, the ata driver doesn't allow for sharing irq1415
: sos since lots of boards doesn't work that way. However if you need
: sos it you can try to add the shared flag in the driver and see if
: sos
sos Well, sortof, the ata driver doesn't allow for sharing irq1415
sos since lots of boards doesn't work that way. However if you need
sos it you can try to add the shared flag in the driver and see if
sos it works on yours. Hmm, maybe I should make this tunable...
It this patch OK?
In message [EMAIL PROTECTED] Mike Smith writes:
:
: sos Well, sortof, the ata driver doesn't allow for sharing irq1415
: sos since lots of boards doesn't work that way. However if you need
: sos it you can try to add the shared flag in the driver and see if
: sos it works on yours. Hmm,
In article [EMAIL PROTECTED], David O'Brien
[EMAIL PROTECTED] wrote:
I don't know what clock_t is used for (kernel version of time_t?).
It was invented by the ANSI/ISO C committee to represent CPU time.
Hardly anything uses it.
John
--
John Polstra
Hi,
I've committed another round of ACPI changes to -current.
The major addition is CPU throttling support. This is implemented using
ACPI, not any vendor-specific technology, so it should work on any
platform that exports the relevant information. By default, the CPU will
run at 100%
: There is absolutely no reason for the ata driver not to simply set
: RF_SHAREABLE and be done with it. It's up to the driver's parent (isa,
: pci, etc) to decide whether the interrupt is in fact shareable or not.
:
: The ata driver itself can share interrupts just fine, and it should
In message [EMAIL PROTECTED] Peter Wemm writes:
: The upshot of this is that drivers should be setting RF_SHAREABLE if they
: themselves can handle the possibility that the motherboard is wired up for
: sharing their IRQ. It is up to the bus controller to sort out what is
: really electrically
In the web CVS repository, $FreeBSD$ expands to version 1.16
In my local version, $FreeBSD$ is expanded to version 1.15
What could explain this?
As someone already mentioned, you may have -k set for that file.
If you don't know, send us the output of cvs status immio.c.
gh
Jonathon
--
David O'Brien [EMAIL PROTECTED] writes:
OR build a 64-bit long (LP64) x86 gcc and test compile with that also.
BDE found *lots* of 64-bit dirty code using this technique.
Mind revealing how that's done?
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL
* David O'Brien [EMAIL PROTECTED] [010707 18:06] wrote:
On Sat, Jul 07, 2001 at 04:42:49PM -0500, Alfred Perlstein wrote:
I'm going to be giving this code some testing, not that you have to
wait for me to finish, but it seems like no one has stepped forward
to review this. I'd like to see
In message [EMAIL PROTECTED] Mike Smith writes:
: Actually, there is a reason. Ata is special like pcic is special.
: Both of them can have multiple interrupt routing methods. When ata is
: connected directly to the south bridge, it can route ISA interrupts,
: even though it is a pci
On Sat, Jul 07, 2001 at 08:13:57PM -0500, Alfred Perlstein wrote:
I'm not interested in wasting time tracking down bugs for your
arch.
*My* arch?? _OUR_ arches.
Anyhow, the simple fact is that if you're unable to cope with some
instability for a short amount of time you shouldn't be
Finally, if you're so damn concerned about your precious alpha I
expect you or at least ANYONE WHO CARES ABOUT ALPHA TO ASSIST IN
TESTING THESE DIFFS.
HOW THE FSCK AM I TO TEST THEM WHEN I CANNOT EVEN GET TO SINGLE USER??
By testing them before they're committed, obviously.
David -
35 matches
Mail list logo
