headers
David Schultz | 1 Apr 2003 01:54
Picon
Favicon

Re: MIDI

Thus spake Thanjee Neefam <thanjee <at> fastmail.fm>:
> I was very happy when compiling my 5.0 kernel. For the first time "device
> midi" compiled without giving any errors. This abnormal excitement only
> led to misery when I discovered after rebooting that there still was no
> MIDI. 
> Is MIDI going to be implemented soon? Who is working on it? Can I help
> them? (I am not a very good programmer, but I can hack pre existing code,
> and I am good at testing). MIDI is the ONLY thing stopping me from
> running FreeBSD exclusively.

FYI, the non-free OSS driver supports MIDI:

	http://www.opensound.com/bsd.html
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |
headers
jason | 1 Apr 2003 02:50

Upgrading from 5.0-RELEASE to -CURRENT on sparc64 (me too)

Im getting the same thing as
http://groups.google.com/groups?q=+attempt+to+use+poisoned+%22malloc%22+cc1plus&hl=en&lr=lang_en&ie=UTF-8&oe=UTF-8&safe=off&selm=Pine.NEB.3.96L.1030212144405.82101A-100000%40fledge.watson.org.lucky.freebsd.current&rnum=3

when doing a make buildworld..
after cvsupping CURRENT

..
/usr/src/contrib/gcc/config/sparc/sysv4.h:96:1: warning: this is the
location of the previous definition
In file included from
/usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/tconfig.h:11,
                 from
/usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/hconfig.h:2,
                 from
/usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/config.h:1,
                 from
/usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/parse.y:34,
                 from /usr/src/contrib/gcc/cp/spew.c:34:
/usr/src/contrib/gcc/config/elfos.h:594:1: warning: "STRING_ASM_OP"
redefined
In file included from
/usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/tconfig.h:15,
                 from
/usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/hconfig.h:2,
                 from
/usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/config.h:1,
                 from /usr/src/contrib/gcc/cp/spew.c:26:
/usr/src/contrib/gcc/config/sparc/sysv4.h:87:1: warning: this is the
location of the previous definition
In file included from
(Continue reading)

Permalink | Reply | 0 comments |
headers
Juli Mallett | 1 Apr 2003 03:37
Picon
Favicon

Odd issues with USB SmartMedia Reader/Writer (PNY)

I'm really dumb when it comes to CAM, SCSI, USB, and so on, so forgive
if I am being naive...  (Also that would probably explain why I am
having a hard time deciding where this mail should end up... Forgive
me on that account, plz.)

I have a PNY USB SmartMedia reader which works excellently with 5.x
with 8M media, but which blows up with 32M media.  I'd assume this is
due to improper geometry or something, but I really have no idea.
Insert-reinsert produces no change in results, etc.  Below are bits
from dmesg, with the smaller then the larger.

Any insight would be appreciated.  Once this is taken care of, the
weekly reboots into windows to clean off the camera can finally stop...
Out last legitimate use of Windows :)

%%% --> With the 8M SmartMedia
umass0: Alcor Mass Storage Device, rev 1.10/1.00, addr 5
umass0: Get Max Lun not supported (STALLED)
umass0:0:0:-1: Attached to scbus0 as device 0
pass0 at umass-sim0 bus 0 target 0 lun 0
pass0: <Generic USB SMC Reader 1.00> Removable Direct Access SCSI-0 device 
pass0: 1.000MB/s transfers
GEOM: new disk da0
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <Generic USB SMC Reader 1.00> Removable Direct Access SCSI-0 device 
da0: 1.000MB/s transfers
da0: 7MB (16000 512 byte sectors: 64H 32S/T 7C)
(da0:umass-sim0:0:0:0): READ(6)/WRITE(6) not supported, increasing minimum_cmd_size to 10.
[0] f:80 typ:1 s(CHS):0/1/10 e(CHS):249/3/16 s:25 l:15975
[1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
(Continue reading)

Permalink | Reply | 4 comments |
headers
Jeff Roberson | 1 Apr 2003 03:28

New threading code.

The kernel components for the 1:1 threading implementation are in the
tree.  This includes the thr system calls, the umtx implementation, and
all of the signal changes.

I will commit the library shortly.  This is all 'beta' quality.  It runs
mozilla and openoffice without issue.  There are known bugs which I will
point out when libthr is in the tree.

More to come.

Cheers,
Jeff

_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Mike Barcroft | 1 Apr 2003 05:26

sparc64 tinderbox failure

Tinderbox FAQ: http://people.FreeBSD.org/~mike/tinderbox.html

--------------------------------------------------------------
>>> 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 /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc64/usr/include
--------------------------------------------------------------
>>> stage 4: building libraries
--------------------------------------------------------------
>>> stage 4: make dependencies
--------------------------------------------------------------
>>> stage 4: building everything..
--------------------------------------------------------------
===>
bin/ps
/tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc64/usr/lib/libkvm.a(kvm_proc.o)(.text+0x794):
undefined reference to `SIGANDSET'
*** Error code 1

Stop in /tinderbox/sparc64/src/bin/ps.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jeff Roberson | 1 Apr 2003 05:54

libthr and 1:1 threading.

I have commited libthr.  To try this out you'll need to do the following

1.  cvsup
2.  rebuild world and kernel
3.  install world and kernel
4.  build libthr from src/lib/libthr
5.  Either replace /usr/lib/libc_r.so.5 with /usr/lib/libthr.so.1 or
relink your applications against libthr.so.1

This works with mozilla and open office.

Known errata:
1.  Mutex priority inheritance is not implemented.
2.  If you mess with the mutex or condvar queues from a signal handler you
will break.
3.  If you reset the sigaction for SIGTHR you will break things.
4.  The scheduling parameters lie.
5.  The garbage collector deadlocks.  We never free threads.  You will
eventually leak memory or run out of LDT entries.
6.  This is x86 only for a short while.
7.  Some of the code is ugly.

I will be addressing all of this shortly.  Feel free to try it out and
report bugs that are not mentioned above.

Cheers,
Jeff

_______________________________________________
freebsd-current <at> freebsd.org mailing list
(Continue reading)

Permalink | Reply | 64 comments |
headers
Scott Carmichael | 1 Apr 2003 06:42

5.0-Current build failing on libkvm

I just cvsup'd today and am now getting this error and subsequent fails...
:(

Anyone have any ideas? (please keep me in the reply as I'm not subscribed
to -current)

cc -O -pipe -march=pentium4 -DLAZY_PS   -Wsystem-headers -Werror -Wall
-Wno-format-y2k -Wno-uninitialized   -static -o ps fmt.o keyword.o nlist.o
print.o ps.o -lm -lkvm
/usr/obj/usr/src/i386/usr/lib/libkvm.a(kvm_proc.o)(.text+0x948): undefined
reference to `SIGANDSET'

_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 8 comments |
headers
Jeff Roberson | 1 Apr 2003 06:50

Re: 5.0-Current build failing on libkvm

On Mon, 31 Mar 2003, Scott Carmichael wrote:

> I just cvsup'd today and am now getting this error and subsequent fails...
> :(
>
> Anyone have any ideas? (please keep me in the reply as I'm not subscribed
> to -current)
>
>
> cc -O -pipe -march=pentium4 -DLAZY_PS   -Wsystem-headers -Werror -Wall
> -Wno-format-y2k -Wno-uninitialized   -static -o ps fmt.o keyword.o nlist.o
> print.o ps.o -lm -lkvm
> /usr/obj/usr/src/i386/usr/lib/libkvm.a(kvm_proc.o)(.text+0x948): undefined
> reference to `SIGANDSET'

Sorry, this was my fault.  I totally spaced on this bit.  You can cvsup
again when your mirror picks up my fix or you can change that SIGANDSET in
kvm_proc.c to SIGSETOR.

Cheers,
Jeff

_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 6 comments |
headers
Matthew Dillon | 1 Apr 2003 10:06

Re: Odd issues with USB SmartMedia Reader/Writer (PNY)

    It's likely that a quirk entry is needed for that smart media 
    device.  Most smart media USB devices require quirk entries in
    CAM.  Many such devices simply lockup permanently (until you unplug
    and replug them in) when sent an unsupported command so without the
    quirk entry anything can happen after the first reported failure.

					-Matt
					Matthew Dillon 
					<dillon <at> backplane.com>

:
:I'm really dumb when it comes to CAM, SCSI, USB, and so on, so forgive
:if I am being naive...  (Also that would probably explain why I am
:having a hard time deciding where this mail should end up... Forgive
:me on that account, plz.)
:
:I have a PNY USB SmartMedia reader which works excellently with 5.x
:with 8M media, but which blows up with 32M media.  I'd assume this is
:due to improper geometry or something, but I really have no idea.
:Insert-reinsert produces no change in results, etc.  Below are bits
:from dmesg, with the smaller then the larger.
:
:Any insight would be appreciated.  Once this is taken care of, the
:weekly reboots into windows to clean off the camera can finally stop...
:Out last legitimate use of Windows :)
:
:%%% --> With the 8M SmartMedia
:umass0: Alcor Mass Storage Device, rev 1.10/1.00, addr 5
:umass0: Get Max Lun not supported (STALLED)
:umass0:0:0:-1: Attached to scbus0 as device 0
(Continue reading)

Permalink | Reply | 0 comments |
headers
Scott Carmichael | 1 Apr 2003 10:07

Re: 5.0-Current build failing on libkvm

Sigh... It seems that there's a lot of problems in -current right now.
First there was a double-line comment problem with a .h file, seems fixed
now, but then there's also an ununsed var in sys/kern/kern_sig.c (line
184), which I fixed and am trying to compile again... for the 3rd time.

Someone wanna get that one in CVS?

On Mon, 31 Mar 2003, Jeff Roberson wrote:

> On Mon, 31 Mar 2003, Scott Carmichael wrote:
>
> > I just cvsup'd today and am now getting this error and subsequent fails...
> > :(
> >
> > Anyone have any ideas? (please keep me in the reply as I'm not subscribed
> > to -current)
> >
> >
> > cc -O -pipe -march=pentium4 -DLAZY_PS   -Wsystem-headers -Werror -Wall
> > -Wno-format-y2k -Wno-uninitialized   -static -o ps fmt.o keyword.o nlist.o
> > print.o ps.o -lm -lkvm
> > /usr/obj/usr/src/i386/usr/lib/libkvm.a(kvm_proc.o)(.text+0x948): undefined
> > reference to `SIGANDSET'
>
> Sorry, this was my fault.  I totally spaced on this bit.  You can cvsup
> again when your mirror picks up my fix or you can change that SIGANDSET in
> kvm_proc.c to SIGSETOR.
>
> Cheers,
> Jeff
(Continue reading)

Permalink | Reply | 4 comments |

Gmane