headers
Julian Elischer | 1 Mar 2004 02:01

HEADSUP!!! USB MFC committed..


The USB code in RELENG_4 has been updated to match that in -current.
Please test any USB devices that are critical to you BEFORE we release
4.10 :-)

thanks

Julian

_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Christopher Vance | 1 Mar 2004 02:11

Re: HEADSUP!!! USB MFC committed..

On Sun, Feb 29, 2004 at 05:01:28PM -0800, Julian Elischer wrote:
>The USB code in RELENG_4 has been updated to match that in -current.
>Please test any USB devices that are critical to you BEFORE we release
>4.10 :-)

<gentle flame="no">
Would the effort to keep making 4.X releases be better spent making
5.X stable, or are the two efforts not competing for the same
developer resources?
</gentle>

--

-- 
Christopher Vance
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Permalink | Reply | 5 comments |
headers
Julian Elischer | 1 Mar 2004 02:18

Re: HEADSUP!!! USB MFC committed..


On Sun, 29 Feb 2004, Julian Elischer wrote:

> 
> The USB code in RELENG_4 has been updated to match that in -current.
> Please test any USB devices that are critical to you BEFORE we release
> 4.10 :-)

p.s. there are some more MFCs to come but they are minor
(except for what looks like a major rewrite of parts of umass)

> 
> 
> thanks
> 
> Julian
> 
> 
> _______________________________________________
> freebsd-hackers <at> freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"
> 

_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
(Continue reading)

Permalink | Reply | 0 comments |
headers
Wes Peters | 1 Mar 2004 02:21

Re: nVidia Riva TNT2 M64 problem on FreeBSD4.9

On Sunday 29 February 2004 08:29 am, Yuri Grebenkin wrote:
> Hi. I've bought a ATI Radion 9000 64Mb and now I'm happy! It runs
> movies of any kind with postprocessing. I've already tested it by
> running Quake2 and Quake3arena with Wine under FreeBSD 4.9. They both
> are looking more alive than under Windows with nVidia TNT2! Even more
> if you believe top, 60% of CPU is idle while playing Quake2 with Wine!
> (Coppermine 900, heated to 1008MHz, 112MHz external)

You are aware that the TNT2 is 3 or 4 generations old Nvidia hardware, 
right?  While the Radeon 9000 series is current?

--

-- 

        Where am I, and what am I doing in this handbasket?

Wes Peters                                               wes <at> softweyr.com
_______________________________________________
freebsd-questions <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Garance A Drosehn | 1 Mar 2004 03:35
Picon
Favicon

Re: HEADSUP!!! USB MFC committed..

At 12:11 PM +1100 3/1/04, Christopher Vance wrote:
>On Sun, Feb 29, 2004, Julian Elischer wrote:
>>The USB code in RELENG_4 has been updated to match that
>>in -current.  Please test any USB devices that are critical
>>to you BEFORE we release 4.10 :-)
>
><gentle flame="no">
>Would the effort to keep making 4.X releases be better spent
>making 5.X stable, or are the two efforts not competing for
>the same developer resources?
></gentle>

This is a very useful project for a subset of FreeBSD users
who need better USB support, and who are not going to jump
to 5.x right away.  If Julian wants to work on this, I think
it's a fine project to do.  [well, assuming he doesn't BREAK
anything!  :-) ]

There's always a long list of important projects to work on,
and each developer has a different priority for which are
the "most worthy" projects to tackle.  Julian *has* been
working on improvements to -current, but right now this is
the item at the top of his list, due to the users that he
deals with the most.  I see no problem.

Since this is a volunteer project, Julian will "make the time"
to work on the projects at the top of his priority list.  So,
since he's volunteering to work on what he wants to work on,
we are not losing any time by letting him volunteer his time
on this weekend to do this particular improvement for some of
(Continue reading)

Permalink | Reply | 0 comments |
headers
Richard Coleman | 1 Mar 2004 05:38
Picon

Re: HEADSUP!!! USB MFC committed..

Christopher Vance wrote:
> On Sun, Feb 29, 2004 at 05:01:28PM -0800, Julian Elischer wrote:
> 
>> The USB code in RELENG_4 has been updated to match that in -current.
>> Please test any USB devices that are critical to you BEFORE we release
>> 4.10 :-)
> 
> 
> <gentle flame="no">
> Would the effort to keep making 4.X releases be better spent making
> 5.X stable, or are the two efforts not competing for the same
> developer resources?
> </gentle>

Keeping the code bases closer together will probably make development 
easier, not harder.  Also, this USB code will now be tested on more 
hardware before the release of 4.10 or 5.3.  I wouldn't be surprised if 
someone running -stable on strange hardware finds a bug that needs 
fixing on both -stable and -current.

Seems like a win/win to me.

Richard Coleman
richardcoleman <at> mindspring.com

_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
(Continue reading)

Permalink | Reply | 3 comments |
headers
Christopher Vance | 1 Mar 2004 05:42

Re: HEADSUP!!! USB MFC committed..

On Sun, Feb 29, 2004 at 11:38:04PM -0500, Richard Coleman wrote:
>Keeping the code bases closer together will probably make development 
>easier, not harder.  Also, this USB code will now be tested on more 
>hardware before the release of 4.10 or 5.3.  I wouldn't be surprised if 
>someone running -stable on strange hardware finds a bug that needs 
>fixing on both -stable and -current.
>
>Seems like a win/win to me.

Okay: that leaves me a happy little vegemite.  :-)

[I had just been growing concerned that 5-STABLE was slipping into the
next decade...]

--

-- 
Christopher Vance
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Permalink | Reply | 2 comments |
headers
Wes Peters | 1 Mar 2004 06:47

Re: HEADSUP!!! USB MFC committed..

On Sunday 29 February 2004 05:18 pm, Julian Elischer wrote:
> On Sun, 29 Feb 2004, Julian Elischer wrote:
> > The USB code in RELENG_4 has been updated to match that in -current.
> > Please test any USB devices that are critical to you BEFORE we
> > release 4.10 :-)
>
> p.s. there are some more MFCs to come but they are minor
> (except for what looks like a major rewrite of parts of umass)

1) You're going to make umass reliable?  Excellent.

2) Will you "MFS" this?  ;^) ;^)
   (Or optionally do it in -CURRENT and then MFC it.)

--

-- 

        Where am I, and what am I doing in this handbasket?

Wes Peters                                               wes <at> softweyr.com
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
FreeBSD Tinderbox | 1 Mar 2004 07:46
Picon
Favicon

[releng_4 tinderbox] failure on i386/i386

TB --- 2004-03-01 05:33:22 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2004-03-01 05:33:22 - starting RELENG_4 tinderbox run for i386/i386
TB --- 2004-03-01 05:33:22 - checking out the source tree
TB --- 2004-03-01 05:33:22 - cd /home/tinderbox/sandbox/RELENG_4/i386/i386
TB --- 2004-03-01 05:33:22 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src
TB --- 2004-03-01 05:52:16 - building world
TB --- 2004-03-01 05:52:16 - cd /home/tinderbox/sandbox/RELENG_4/i386/i386/src
TB --- 2004-03-01 05:52:16 - /usr/bin/make -B buildworld
>>> Rebuilding the temporary build tree
>>> stage 1: bootstrap tools
>>> stage 2: cleaning up the object tree
>>> stage 2: rebuilding the object tree
>>> stage 2: build tools
>>> stage 3: cross tools
>>> stage 4: populating /home/tinderbox/sandbox/RELENG_4/i386/i386/obj/other/tinderbox/RELENG_4/i386/i386/src/i386/usr/include
>>> stage 4: building libraries
>>> stage 4: make dependencies
>>> stage 4: building everything..
TB --- 2004-03-01 06:31:45 - building generic kernel
TB --- 2004-03-01 06:31:45 - cd /home/tinderbox/sandbox/RELENG_4/i386/i386/src
TB --- 2004-03-01 06:31:45 - /usr/bin/make buildkernel KERNCONF=GENERIC
>>> Kernel build for GENERIC started on Mon Mar  1 06:31:45 GMT 2004
>>> Kernel build for GENERIC completed on Mon Mar  1 06:39:49 GMT 2004
TB --- 2004-03-01 06:39:50 - building LINT kernel
TB --- 2004-03-01 06:39:50 - cd /home/tinderbox/sandbox/RELENG_4/i386/i386/src
TB --- 2004-03-01 06:39:50 - /usr/bin/make buildkernel KERNCONF=LINT
>>> Kernel build for LINT started on Mon Mar  1 06:39:53 GMT 2004
[...]
cc -c -O -pipe  -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes
-Wpointer-arith -Winline -Wcast-qual  -fformat-extensions -ansi  -nostdinc -I- -I.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Rob | 1 Mar 2004 12:18
Picon

CLOCK_REALTIME incorrectly in sys/time.h ?


Hi,

When compiling a certain software, I come across following bug in FreeBSD 4.x,
when it wants to check the presence of the definition of CLOCK_REALTIME in
time.h:

     # FreeBSD 4.X incorrectly puts the header into sys/time.h;
     # time.h is required (see pages 45 and 46 in the POSIX standard).

Is it worth fixing this in the next 4.X release ?
How is this in 5.X ?

Regards,
Rob.
_______________________________________________
freebsd-stable <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |

Gmane