Touchpad support in -current for Sony Vaio GRX-670
Seems the 670 needs a slight addition to psm.c for its
touchpad. Can this be committed?
I'm using Yahoo because the mailing list doesn't like
my "real" address. Please excuse the formatting.
*** /usr/src/sys/isa/psm.c Thu Dec 12 21:35:39
2002
--- psm.c Fri Nov 29 01:49:22 2002
***
*** 2880,2885
--- 2880,2886
{ 0x80374d24, "IBM PS/2 mouse port"
},/*IBM3780,ThinkPad */
{ 0x81374d24, "IBM PS/2 mouse port"
},/*IBM3781,ThinkPad */
{ 0x0490d94d, "SONY VAIO PS/2 mouse
port"},/*SNY9004,Vaio*/
+ { 0x0390d94d, "SONY VAIO PS/2 mouse
port"},/*SNY9003,VaioGRX670*/
{ 0 }
};
__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: i386 tinderbox failure
On Sat, 28 Dec 2002, Bruce Evans wrote: > > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:932: (near initialization for >`devfs_specop_entries[14]') > > *** Error code 1 > > This was broken by removing a unsed definition in: > > % RCS file: /home/ncvs/src/sys/kern/vnode_if.src,v > % Working file: vnode_if.src > % head: 1.59 > % ... > % > % revision 1.59 > % date: 2002/12/24 19:47:13; author: rwatson; state: Exp; lines: +0 -9 > % Flush vop_refreshlabel() definition, since it is no longer used. > % > % Obtained from: TrustedBSD Project > % Sponsored by: DARPA, Network Associates Laboratories > % > > The use is just a stub so it should have been removed too. Yup, I missed it in an earlier GC pass. I've now removed it -- sorry about the breakage. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: i386 tinderbox failure
On Fri, 27 Dec 2002, Dag-Erling Smorgrav wrote: > -- > >>> Rebuilding the temporary build tree > -- > [... 4421 lines of machine-generated spam deleted] Please fix the tinderbox so that it doesn't include full makeworld output. > cc1: warnings being treated as errors > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:76: warning: `struct >vop_refreshlabel_args' declared inside parameter list > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:76: warning: its scope is only >this definition or declaration, which is probably not what you want > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c: In function `devfs_refreshlabel': > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:668: argument `ap' doesn't match >prototype > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:76: prototype declaration > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c: At top level: > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:897: `vop_refreshlabel_desc' >undeclared here (not in a function) > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:897: initializer element is not >constant > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:897: (near initialization for >`devfs_vnodeop_entries[15].opve_op') > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:897: initializer element is not >constant > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:897: (near initialization for >`devfs_vnodeop_entries[15]') > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:899: initializer element is not >constant > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:899: (near initialization for >`devfs_vnodeop_entries[16]') > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:900: initializer element is not >constant > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:900: (near initialization for >`devfs_vnodeop_entries[17]') > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:902: initializer element is not >constant > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:902: (near initialization for >`devfs_vnodeop_entries[18]') > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:904: initializer element is not >constant > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:904: (near initialization for >`devfs_vnodeop_entries[19]') > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:905: initializer element is not >constant > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:905: (near initialization for >`devfs_vnodeop_entries[20]') > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:906: initializer element is not >constant > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:906: (near initialization for >`devfs_vnodeop_entries[21]') > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:923: `vop_refreshlabel_desc' >undeclared here (not in a function) > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:923: initializer element is not >constant > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:923: (near initialization for >`devfs_specop_entries[8].opve_op') > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:923: initializer element is not >constant > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:923: (near initialization for >`devfs_specop_entries[8]') > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:925: initializer element is not >constant > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:925: (near initialization for >`devfs_specop_entries[9]') > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:926: initializer element is not >constant > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:926: (near initialization for >`devfs_specop_entries[10]') > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:927: initializer element is not >constant > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:927: (near initialization for >`devfs_specop_entries[11]') > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:929: initializer element is not >constant > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:929: (near initialization for >`devfs_specop_entries[12]') > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:931: initializer element is not >constant > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:931: (near initialization for >`devfs_specop_entries[13]') > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:932: initializer element is not >constant > /local0/scratch/des/src/sys/fs/devfs/devfs_vnops.c:932: (near initialization for >`devfs_specop_entries[14]') > *** Error code 1 This was broken by removing a unsed definition in: % RCS file: /home/ncvs/src/sys/kern/vnode_if.src,v % Working file: vnode_if.src % head: 1.59 % ... % % revision 1.59 % date: 2002/12/24 19:47:13; author: rwatson; state: Exp; lines: +0 -9 % Flush vop_refreshlabel() definition, since it is no longer used. % % Obtained from:
subscribe
subscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
anyone using the ng_fec node?
I have some changes to make to this node and would like to find someone who can test them. Julian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kldunload related panic
During buildworld I loaded and unloaded the if_tun module and here is the result: Kernel is basically GENERIC with some drivers removed, uname: FreeBSD 5.0-RC #0: Fri Dec 27 12:40:30 GMT 2002 panic: allocbuf: buffer not busy panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8:0xc02e9f73 stack pointer = 0x10:0xc63e0c70 frame pointer = 0x10:0xc63e0c70 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 11886 (kldunload) trap number = 12 panic: page fault syncing disks, buffers remaining... panic: allocbuf: buffer not busy Uptime: 28m30s Dumping 63 MB ata0: resetting devices .. done 16 32 48 --- #0 0xc02e31cb in doadump () #1 0xc02e3651 in boot () #2 0xc02e3863 in panic () #3 0xc032454d in allocbuf () #4 0xc0324204 in getblk () #5 0xc03217fa in breadn () #6 0xc03217ac in bread () #7 0xc03edcc3 in ffs_update () #8 0xc0401d7f in ffs_fsync () #9 0xc0400f4e in ffs_sync () #10 0xc033483b in sync () #11 0xc02e32c2 in boot () #12 0xc02e3863 in panic () #13 0xc0458b8e in trap_fatal () #14 0xc04588a2 in trap_pfault () #15 0xc045846d in trap () #16 0xc0449598 in calltrap () #17 0xc02d4a4a in linker_file_unregister_sysctls () #18 0xc02d511e in linker_file_unload () #19 0xc02d57d6 in kldunload () #20 0xc0458e4e in syscall () #21 0xc04495ed in Xint0x80_syscall () Any ideas? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Showing the previous mixer levels when setting new ones...
I've often wanted the subject, so here's a small patch which does things
such as:
(jmallett@luna:~/mixer)10% ./mixer pcm 90
Setting the mixer pcm from 100:100 to 90:90.
(jmallett@luna:~/mixer)11% ./mixer pcm 100
Setting the mixer pcm from 90:90 to 100:100.
I thought about making it not change settings if the old were the same as the
new, but I decided that would be mild overkill, though of course, that's
something someone else might say is useful, so I'd be glad to update the
patch to do the same. I'd like to commit this some time in the next few
days, so it doesn't get lost in my head.
Note that there are many nearby meaning/style bugs regarding "left" and "right"
and what things really are, and it wouldn't hurt to have that all cleared up,
in addition to maybe some macros to give meaningful modes of operation. Just
a thought.
%%%
RCS file: /home/ncvs/src/usr.sbin/mixer/mixer.c,v
retrieving revision 1.16
diff -d -u -r1.16 mixer.c
--- mixer.c 25 Jun 2001 21:06:15 - 1.16
+++ mixer.c 27 Dec 2002 21:33:16 -
@@ -217,8 +217,14 @@
else if (r > 100)
r = 100;
- printf("Setting the mixer %s to %d:%d.\n", names[dev],
- l, r);
+ if (ioctl(baz, MIXER_READ(dev),&bar)== -1) {
+ warn("MIXER_READ");
+ argc--; argv++;
+ continue;
+ }
+
+ printf("Setting the mixer %s from %d:%d to %d:%d.\n",
+ names[dev], bar & 0x7f, (bar >> 8) & 0x7f, l, r);
l |= r << 8;
if (ioctl(baz, MIXER_WRITE(dev), &l) == -1)
%%%
Thanx,
juli.
--
Juli Mallett <[EMAIL PROTECTED]>
OpenDarwin, Mono, FreeBSD Developer.
ircd-hybrid Developer, EFnet addict.
FreeBSD on MIPS-Anything on FreeBSD.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Does anyone have an lge(4) supported NIC?
Hi all. Sorry for cross posting, but if someone on the channel has an lge(4) supported NIC and you are willing to test some patches, can you please contact me privately? Cheers. -- Hiten Pandya http://www.unixdaemons.com/~hiten/ [EMAIL PROTECTED], [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DP2 won't stay powered off
Hey, Nate Sorry about the late reply, but here is my output: hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: S1 hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 0 hw.acpi.s4bios: 1 hw.acpi.verbose: 0 hw.acpi.cpu.max_speed: 2 hw.acpi.cpu.current_speed: 2 hw.acpi.cpu.performance_speed: 2 hw.acpi.cpu.economy_speed: 1 This is from a HP Vei8 computer, and it turns itself on about 20 minutes after a "shutdown -p now". -- Mvh, Frode Nordahl On Thu, 2002-12-05 at 19:37, Nate Lawson wrote: > On Thu, 5 Dec 2002, Mathew Kanner wrote: > > I've noticed some odd behavior when I installed DP2 on my > > machine last night. When I "shutdown -p now", the machine will turn > > itself back-on in about twenty minutes. This would be nice feature if > > I had asked for it. > > Can everyone with the auto power on problem report the output of "sysctl > hw.acpi"? > > -Nate > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
xe pcmcia interface broken
Using an IBM ThinkPad 770 with the Intel EtherExpress(TM) PRO/100 PC Card Mobile Adapter16 is a no go in RELENG_5_0, this worked fine in 4.7-RELEASE also i had to use the "OLDCARD" style pcmcia driver, the new one won't work. pccard: card inserted, slot 0 xe0 at port 0x240-0x24f iomem 0xd4000-0xd4fff irq 3 slot 0 on pccard0 xe0: Intel CE3, bonding version 0x45, 100Mbps capable xe0: DingoID = 0, RevisionID = 0, VendorID = 0 xe0: Ethernet address 00:a0:c9:37:21:ef xe0: watchdog timeout; resetting card Now for the real fun, oversized frames: # ping -c 1 darkstar PING darkstar.sajd.net (192.168.1.11): 56 data bytes 64 bytes from 192.168.1.11: icmp_seq=0 ttl=64 time=0.668 ms # ping -c 1 -s 2000 darkstar PING darkstar.sajd.net (192.168.1.11): 56 data bytes xe0: discard oversize frame (ether type 800 flags 3 len 1518 > max 1514) xe0: discard oversize frame (ether type 800 flags 3 len 1518 > max 1514) # ifconfig xe0 | grep mtu xe0: flags=8843 mtu 1500 any ideas? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DP2 won't stay powered off
On Thu, Dec 05, 2002 at 10:37:49AM -0800, Nate Lawson wrote: > On Thu, 5 Dec 2002, Mathew Kanner wrote: > > I've noticed some odd behavior when I installed DP2 on my > > machine last night. When I "shutdown -p now", the machine will turn > > itself back-on in about twenty minutes. This would be nice feature if > > I had asked for it. > > Can everyone with the auto power on problem report the output of "sysctl > hw.acpi"? I'm seeing the same problem on my T20. It powers on again after some time. But I don't use the DP2! FreeBSD curry.lan.barfoos.de 5.0-RC FreeBSD 5.0-RC #1: Wed Dec 25 23:04:57 CET 2002 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: S1 hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 0 hw.acpi.s4bios: 1 hw.acpi.verbose: 0 hw.acpi.disable_on_poweroff: 1 hw.acpi.cpu.max_speed: 8 hw.acpi.cpu.current_speed: 8 hw.acpi.cpu.performance_speed: 8 hw.acpi.cpu.economy_speed: 4 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 30 hw.acpi.thermal.tz0.temperature: 3582 hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 3647 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 3702 hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.battery.life: 88 hw.acpi.battery.time: -1 hw.acpi.battery.state: 2 hw.acpi.battery.units: 2 hw.acpi.battery.info_expire: 5 hw.acpi.acline: 1 jens -- KeyID=96FE36DB Key fingerprint=1C9B 7EF8 1A22 1740 9F1B AB7B 17D2 64E1 96FE 36DB To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
uthread_info.c typos patch
Hi,
There are a few typos in the comments for uthread_info.c
--
Craig Rodrigues
http://www.gis.net/~craigr
[EMAIL PROTECTED]
Index: uthread_info.c
===
RCS file: /home/ncvs/src/lib/libc_r/uthread/uthread_info.c,v
retrieving revision 1.23
diff -u -r1.23 uthread_info.c
--- uthread_info.c 2002/10/20 22:49:06 1.23
+++ uthread_info.c 2002/12/27 17:11:11
@@ -103,9 +103,9 @@
continue;
/*
* We only need to continue in case of
-* EEXIT error. Most other error
+* EEXIST error. Most other error
* codes means that we will fail all
-* the times.
+* the time.
*/
return;
} else {
sparc64 tinderbox failure
-- >>> 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.. -- >>> Kernel build for GENERIC started on Fri Dec 27 16:12:52 GMT 2002 -- ===> ipfilter /tinderbox/sparc64/src/sys/ufs/ffs/ffs_subr.c: In function `ffs_load_inode': /tinderbox/sparc64/src/sys/ufs/ffs/ffs_subr.c:114: argument `mtype' doesn't match prototype /tinderbox/sparc64/src/sys/ufs/ffs/ffs_extern.h:73: prototype declaration /tinderbox/sparc64/src/sys/ufs/ffs/ffs_subr.c:114: argument `fs' doesn't match prototype /tinderbox/sparc64/src/sys/ufs/ffs/ffs_extern.h:73: prototype declaration /tinderbox/sparc64/src/sys/ufs/ffs/ffs_subr.c:114: number of arguments doesn't match prototype /tinderbox/sparc64/src/sys/ufs/ffs/ffs_extern.h:73: prototype declaration *** Error code 1 Stop in /tinderbox/sparc64/obj/tinderbox/sparc64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/sparc64/src. *** Error code 1 Stop in /tinderbox/sparc64/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/ufs/ffs ffs_vfsops.c
In message <[EMAIL PROTECTED]>, Poul-Henning Kamp writes: >phk 2002/12/27 03:05:05 PST > > Modified files: >sys/ufs/ffs ffs_vfsops.c > Log: > Use three UMA zones for FFS/UFS inodes instead of malloc space. > Since inodes are currently 144 bytes, this will save 112 bytes per > inode. This can amount to up to 10MByte on large systems. All things considered, I have a hard time telling if this will result in a performance improvement (apart from the memory savings) or not. There are a lot of indications which point in opposite directions so I think it will be a wash. I considered making the zones per mountpoint, but decided against it for now, so for now all FFS/UFS filesystms share these three zones. You can monitor these zones with: syv# sysctl vm.zone | sed -n -e 2p -e /FFS/p ITEMSIZE LIMIT USEDFREE REQUESTS FFS2 dinode: 256,0, 17200, 95,97431 FFS1 dinode: 128,0, 0, 0,0 FFS inode: 144,0, 17200,104,97431 But be aware that the USED count is number of items in the zone, not number of items allocated from the zone. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT: buildworld failure: sbin/swapon
On Fri, Dec 27, 2002 at 05:42:25AM +, Daniel Flickinger wrote: > ...because I have been building BSD in the development track > for 20+ years from BSD 2.+ for PDPs on through --and it > works, _consistently_. If I don't take the build, I move the > old one back in place. I don't get unnecessary unreferenced > variables, etc. --and, yes, I know that obj [supposedly] > uses its own includes ... if it does, fine; if not, it's > available in /usr/include. > > Consistency may be the hobgoblin of a little mind, but I'll > live with it. Well, -current builds fine for me using the 'proper' mechanism, so if you want to be different you're basically on your own :-) Kris msg49354/pgp0.pgp Description: PGP signature
Error installing 5.0-RC2 over NFS
Hi, I had a mysterious problem when I try to install from the 5.0-RC2 floppies over NFS. The "Loading module if_awi.ko failed" message is well known as I can see :-) But when I had configured my network (xl0 inet 10.62.10.23 netmask 255.255.255.0) using sysinstalls mask and bring it up right now, mount_nfs fails with the message: mount_nfs: can't update /var/db/mounttab for 10.62.10.72:/cdrom mount_nfs: /dist: no such file or directory Does anyone know how to fix or workaround? Jens -- L i W W W i Jens Rehsack LW W W L i W W W W i nnnLiWing IT-Services L iW W W Wi n n g g i W W i n n g gFriesenstraße 2 06112 Halle g g g Tel.: +49 - 3 45 - 5 17 05 91ggg e-Mail: <[EMAIL PROTECTED]> Fax: +49 - 3 45 - 5 17 05 92http://www.liwing.de/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: WEIRD! div() broken on -CURRENT?
Andy Sparrow ([EMAIL PROTECTED]) napisał(a): > > Hmm, I've been running GATOS binary modules built for Linux to provide > XV support for an ATI Mobility Pro LY for some time (at least 6-8 months > and some 4-5 different "experimental" versions so far, all have worked > great): Btw. GATOS compiles from source fine for me (I use extracted X server port for that). I use driver compiled from GATOS CVS two months ago fine on my VAIO FX-604 without any problems. -- << Marcin Cieslak // [EMAIL PROTECTED] >> msg49352/pgp0.pgp Description: PGP signature
