Hello,
after the following patch:
joe 2002/02/15 16:51:26 PST
Modified files:
sys/dev/usb ohci.c uhci.c usb.h usb_subr.c usbdivar.h
Log:
Merge from NetBSD:
Pave the way for USB2, by replacing 'lowspeed' with 'speed', so
that it can take the values USB_SPEED_LOW,
Bruce Evans wrote:
> On Sat, 16 Feb 2002, Terry Lambert wrote:
> > PHK was threatening to murder /dev/speaker to work
> > around some clock issues that would be hard to nail
> > down the right way.
>
> I think you mean /dev/pcaudio.
Yes; I confused the two, since I rarely do audio stuff
at all (
Fcc: outbox
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
> > >
> > > and I got a small tune on attach but nothing on detach.
> > > Now I am unable to play notes on /dev/speaker. Any hint?
>
> As Terry notes, shouldn't possibly be related.
>
> > I have no crashes but th
On Sun, 2002-02-17 at 00:49, Paul van der Zwan wrote:
> I have no crashes but the detach action is never executed when I switch off
> my Sony camera ( it has never worked as far as I know)
> Attach actions are executed fine..
I have not see crashas any more too, BUT now I can't see my usb keyboar
Paul van der Zwan wrote:
> No, but if I run usbd in the foreground and with some -v flags it never
> reports seeing a detach event even though the device driver reports it.
> It looks like usbd just doesn't get it...
[ ... ]
> It looks like the driver works fine as far as I can tell, but usbd ju
I also see these messages on my Dell 410 Workstation at work and a Dual
PIII Box I use at home to do builds with...they just seem to 'come and go'
with no particular pattern to them...I have just been ignoring them for the
most part...they don't really seem to cause any problems..
At 06:54 P
Hi all,
While looking at nis-utils-1.4.1 from linux, I found that that
whole package is based on Bill's work. Intersting that everything there
is GNU labled. What happened to the BSD copyright ? Or has it been GPL'd
from the beginning ?
http://freshmeat.net/projects/nis-utils
The author even f
Bills Work:
http://people.freebsd.org/~wpaul/nis.tar.gz
Suse Linux version:
ftp://ftp.kernel.org/pub/linux/utils/net/NIS+/nis-utils-1.4.1.tar.bz2
An example from a file:
File: db_add_entry.c
Bills Copyright:
/*
* Copyright (c) 1996, 1997
* Bill Paul <[EMAIL PROTECTED]>. All rights
On Sun, 10 Feb 2002, Kevin Day wrote:
>
> I'm the maintainer for ports/editors/joe, and just tried compiling it under
> -CURRENT.
>
> includes which includes ucontext.h
>
> > cc -O -pipe -c umath.c
> > In file included from b.h:6,
> > from bw.h:23,
> > from
Hi,
Two ports I've tried to install recently, open-motif-devel and AbiWord,
have attempted to `mkdir /'. This fails with: "mkdir: /: Is a
directory." Installing these ports works just fine under 4.5-STABLE.
Pete...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-cu
:I just wrote the following fix for some of the overflow problems.
I don't understand how this code is supposed to handle overflows.
You seem only to be checking to see if the master timecounter has
changed to a different type.
-Matt
On Sun, Feb 17, 2002 at 03:57:59PM +0100, Martin Blapp wrote:
> Bill, did you ever allowed them to make it GPL only ? Looking at the code
> it should be possible to import some things and make a NIS+ client
> available. But only if it's not GPL'd.
Interesting. I looked as nisgrep/nisgrep.c and n
Martin Blapp <[EMAIL PROTECTED]> wrote:
> Suse's Copyright:
>
> /* Copyright (c) 1999 Thorsten Kukuk
>Author: Thorsten Kukuk <[EMAIL PROTECTED]>
That would at least be a copyright violation.
--
cheers, J"org .-.-. --... ...-- -.. . DL8DTL
http://www.sax.de/~joerg/
In message <[EMAIL PROTECTED]>, Bruce Evans writes:
>> This occurs both with and without the gettimeofday Giant-removal patch, so
>> I am fairly sure it has nothing to do with any of my current work. This is
>> running -current on a DELL2550 (2xCPUs), compiled with the SMP option.
The Gian remo
In message <[EMAIL PROTECTED]>, Matthew Dillon wri
tes:
>:I just wrote the following fix for some of the overflow problems.
>
>I don't understand how this code is supposed to handle overflows.
>You seem only to be checking to see if the master timecounter has
>changed to a different ty
Ok, I've looked at the code more carefully and I understand how this
works now. However, it is not enough in an SMP environment. You
need a generation count in the timecounter structure and you also need
a synchronization point when you switch time counters or a process
runni
:Bruce's patch amounts to a retry if the current timecounter was updated
:while we were calculating time. It is a bit more defensive than it
:needs to be and generally pessimizes the timecounters elegant lockless
:design a fair bit, but it is still much better than slamming a mutex
:around the en
Whoop! I take it back. I'm still getting the errors:
microuptime() went backwards (458.168990 -> 458.168882)
microuptime() went backwards (578.609995 -> 577.929801)
microuptime() went backwards (748.912755 -> 748.237402)
microuptime() went backwards (775.159625 -> 775.159612)
I also th
In message <[EMAIL PROTECTED]>, Matthew Dillon wri
tes:
>However, I think to be complete we need to make it even less elegant.
>The TC module is only flip-flopping between two time counters, which
>means that it can flip-flop twice and the test will not work. We need
>a generatio
In message <[EMAIL PROTECTED]>, Matthew Dillon wri
tes:
>Whoop! I take it back. I'm still getting the errors:
>
>microuptime() went backwards (458.168990 -> 458.168882)
>microuptime() went backwards (578.609995 -> 577.929801)
>microuptime() went backwards (748.912755 -> 748.237402)
>microupt
Matt,
Easy now, there is more depth to it than that... I have promised myself
to get the timecounter paper written and I'll probably present it at
BSDcon-euro-2002 in Amsterdam if they want to listen to me.
For now, lets concentrate on the PIIX hardware because that's where
the problem seems t
I'm about to begin the import of sendmail 8.12.2 into -CURRENT. While I am
doing the important, it's likely that a buildworld will fail. I'll post
again when I'm done (expected to take about 15 to 20 minutes).
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in
whoever wrote:
> Sorry work kept me from getting back to you immediately
> following is the error i am getting
> i cvsuped the src on February 7th
>
>
> Version of my vfs_syscall
> $FreeBSD: src/sys/kern/vfs_syscalls.c,v 1.220 2002/02/01 18:27:16 alfred Exp
Are you sure you actu
> If this patch cures the PIIX problem, something I'm not at all convinced
> about, it should go in, if not only the comment should go in.
I would like to see "the PIIX problem" caught on camera, personally.
We're aware of one errata for it already, and we work around it. If
there's another p
gshapiro> I'm about to begin the import of sendmail 8.12.2 into -CURRENT.
gshapiro> While I am doing the important, it's likely that a buildworld
gshapiro> will fail. I'll post again when I'm done (expected to take about
gshapiro> 15 to 20 minutes).
The import and infrastructure commits are comp
:I would like to see "the PIIX problem" caught on camera, personally.
:We're aware of one errata for it already, and we work around it. If
:there's another problem, or ideally if someone has some relatively quick
:code to test it, that would be much better.
If the _safe version works I'
:I would like to see "the PIIX problem" caught on camera, personally.
:We're aware of one errata for it already, and we work around it. If
:there's another problem, or ideally if someone has some relatively quick
:code to test it, that would be much better.
Holy shit. We are screwed.
>
> :I would like to see "the PIIX problem" caught on camera, personally.
> :We're aware of one errata for it already, and we work around it. If
> :there's another problem, or ideally if someone has some relatively quick
> :code to test it, that would be much better.
>
> Holy shit. We
Ok, here is a patch that executes a brute-force solution to the
asynchronous counter problem.
Basically it figures out a mask and then the timer code loops until two
masked reads yield the same value, guarenteeing that we haven't caught
the timer during a carry.
On my sys
:Sounds like we need to smack whoever made your chipset as well. Intel
:learned their lesson (finally) with later revisions of the PIIX4. I'm
:guessing you're running this against a ServerWorks system.
atapci0: port 0x8b0-0x8bf at device 15.1 on
pci0
Uh huh.
It might be possible
In message <[EMAIL PROTECTED]>, Matthew Dillon wri
tes:
>
>:I would like to see "the PIIX problem" caught on camera, personally.
>:We're aware of one errata for it already, and we work around it. If
>:there's another problem, or ideally if someone has some relatively quick
>:code to test it,
> Ok, here is a patch that executes a brute-force solution to the
> asynchronous counter problem.
>
> Basically it figures out a mask and then the timer code loops until two
> masked reads yield the same value, guarenteeing that we haven't caught
> the timer during a carry.
>
sendmail 8.12.2 has been imported into -CURRENT.
sendmail 8.12 has been developed with two main topics in mind: enhanced
security and better performance. sendmail is by default not set-user-ID
root anymore which avoids potential local root exploits. See
/etc/mail/README (after running mergemast
> >:I would like to see "the PIIX problem" caught on camera, personally.
> >:We're aware of one errata for it already, and we work around it. If
> >:there's another problem, or ideally if someone has some relatively quick
> >:code to test it, that would be much better.
> >
> >Holy shit.
:
:I have some reservations about this, because I'm not sure that 10
:successive reads will catch the ripple-counter problem that the old PIIX4s
:have.
Just goes to show that I need to document my code :-)
Those reads are not detecting the ripple-counter problem, they are
figuring o
On Sun, 17 Feb 2002, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Bruce Evans writes:
>
> >> This occurs both with and without the gettimeofday Giant-removal patch, so
> >> I am fairly sure it has nothing to do with any of my current work. This is
> >> running -current on a DELL255
On Sun, 17 Feb 2002, Matthew Dillon wrote:
> Ok, I've looked at the code more carefully and I understand how this
> works now. However, it is not enough in an SMP environment. You
> need a generation count in the timecounter structure and you also need
> a synchronization point
On Sun, 17 Feb 2002, Matthew Dillon wrote:
> Whoop! I take it back. I'm still getting the errors:
>
> microuptime() went backwards (458.168990 -> 458.168882)
> microuptime() went backwards (578.609995 -> 577.929801)
> microuptime() went backwards (748.912755 -> 748.237402)
> microuptime() w
Is there a single document, or small set of documents, that describes getting
started kernel hacking on FreeBSD? How about a set of URLs?
I would like something that tells me about (in no particular order)
1) debugging over the serial line, and remote debugging in general
2) Building for 5.0 o
>Date: Sun, 17 Feb 2002 17:43:55 -0800
>From: "George V. Neville-Neil" <[EMAIL PROTECTED]>
>Is there a single document, or small set of documents, that describes getting
>started kernel hacking on FreeBSD? How about a set of URLs?
>I would like something that tells me about (in no particular or
+---[ Joerg Wunsch ]--
| Martin Blapp <[EMAIL PROTECTED]> wrote:
|
| > Suse's Copyright:
| >
| > /* Copyright (c) 1999 Thorsten Kukuk
| >Author: Thorsten Kukuk <[EMAIL PROTECTED]>
|
| That would at least be a copyright violation.
Not necessarily, some derived works
|whoever wrote:
|
|> Sorry work kept me from getting back to you immediately
|> following is the error i am getting
|> i cvsuped the src on February 7th
| >
|> > Version of my vfs_syscall
|> $FreeBSD: src/sys/kern/vfs_syscalls.c,v 1.220 2002/02/01 18:27:16 alfred Exp
|
|Are you sure
whoever wrote:
> absolutely.
> I just checked again the kernel causing this trouble was built after
> cvsuping. And I am pretty sure I did the make world after
> cvsupping too. I dont know how to check for that though.
> Just out of curiosity should make world matter
> in this instance. is the
...
sio0 at port 0x3f8-0x3ff irq 4 on isa0
sio0: type 16550A, console
sio0: interrupting at ISA irq 4
sio1: reserved for low-level i/o
vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounter "i8254" frequency 1193182 Hz
ata0-slave: timeout waiting for interrupt
ata0-slave: ATAPI iden
On Sun, Feb 17, 2002 at 10:07:34PM -0800, Peter Wemm wrote:
> ...
> sio0 at port 0x3f8-0x3ff irq 4 on isa0
> sio0: type 16550A, console
> sio0: interrupting at ISA irq 4
> sio1: reserved for low-level i/o
> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0
> Timecounter "i8254" frequency 1
Andrew Kenneth Milton wrote:
> There is unfortunately a section of the GPL community who confuses this
> with the right to simply relicense BSDL code whenever you want, because it
> doesn't explicitly deny it. The FSF 'GPL compatible' licenses page makes
> this even more confusing (IMO).
>
> If y
+---[ Terry Lambert ]--
| Andrew Kenneth Milton wrote:
| > There is unfortunately a section of the GPL community who confuses this
| > with the right to simply relicense BSDL code whenever you want, because it
| > doesn't explicitly deny it. The FSF 'GPL compatible' license
Andrew Kenneth Milton wrote:
> | The FSF is wrong on "compatible".
>
> They're only right in one circumstance. Using whole slabs of BSDL code
> standalone as part of the GPL project, i.e. no mixing of code, the GPL
> forbids that (since you can't relicense other people's code).
Yes, this is actu
48 matches
Mail list logo
