Re: Intel 945GM chipset support
On Wed, 7 Jun 2006 18:34:03 +0300 Vladimir Terziev <[EMAIL PROTECTED]> wrote: > This doesn't sound good :( See 'HDA sound driver mod for thinkpad x60s' thread in -mobile mailing list. > As i found in XOrg's documentation, i945 graphics chip is supported by > i810 XOrg driver, but i suppose the apg support must be provided by the > kernel ?! I810 driver with X.org 6.9.0 supports *i945G* chip. not i945GM. If you want to use i810 driver, you can use this patch when build xorg-server. http://www.alib.jp/files/patch-i945GM.txt -- KONDOU, Kazuhiro @ Ancient library site top URL : http://www.alib.jp/ mail address : [EMAIL PROTECTED] fingerprint = 18CA 90A9 FDEE FBE1 F69A D124 9F95 9289 E665 4D2B ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
help:Makefile template for device drivers with multiple directories
Hi guys: Need your helps again! The following is a Makefile template for a device driver in FreeBSD. But when my driver source codes locate in multiple directories (such as under osd/, engine/, and cam/), how to write the Makefile? I have tried but still can not get through this, please give me a help! Thanks! Hong Note: Makefile template .PATH: . KMOD= shasta SRCS= shasta.c SRCS += device_if.h bus_if.h pci_if.h SRCS += opt_scsi.h opt_cam.h .. .include ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: help:Makefile template for device drivers with multiple directories
On 08.06.2006, at 14:13, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> wrote: Need your helps again! The following is a Makefile template for a device driver in FreeBSD. But when my driver source codes locate in multiple directories (such as under osd/, engine/, and cam/), how to write the Makefile? I have tried but still can not get through this, please give me a help! Are those sources of a single driver, or just subdrivers? FWIW, look at bsd.subdir.mk Or you can try writing SRCS+= osd/something.c engine/something_else.c cam/whatever_that_does.c ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ppc(4) as module
Is there a reason for ppc(4) being only statically compiled in
kernel driver ? It looks like it is trivial to modularize it. Some
time ago I saw the thread about the ppc/acpi related troubles, that
resolves into the acpi being the module, and ppc compiled into the
kernel.
I propose to make the ppc module. Below is the Makefile that
"works for me".
Index: sys/modules/Makefile
===
RCS file: /usr/local/arch/ncvs/src/sys/modules/Makefile,v
retrieving revision 1.490
diff -u -r1.490 Makefile
--- sys/modules/Makefile28 Apr 2006 05:23:10 - 1.490
+++ sys/modules/Makefile8 Jun 2006 16:23:46 -
@@ -190,6 +190,7 @@
${_pmc} \
portalfs \
ppbus \
+ ppc \
ppi \
pps \
procfs \
After the patch, create the sys/modules/ppc directory and place there
the Makefile:
===
# $FreeBSD: src/sys/modules/ppc/Makefile,v 1.1 2003/11/19 05:08:26 kib Exp $
.PATH: ${.CURDIR}/../../dev/ppc
KMOD= ppc
SRCS= bus_if.h device_if.h ppbus_if.h isa_if.h pci_if.h serdev_if.h \
opt_ppc.h opt_isa.h \
ppc_acpi.c ppc_pci.c \
ppc.c ppc_isa.c ppc_puc.c
.include
===
Please, comment.
pgpmP8eHEo4nw.pgp
Description: PGP signature
Re: help:Makefile template for device drivers with multiple directories
On Thursday 08 June 2006 12:13, [EMAIL PROTECTED] wrote:
> Hi guys:
>
>
>
> Need your helps again! The following is a Makefile template for a device
> driver in FreeBSD. But when my driver source codes locate in multiple
> directories (such as under osd/, engine/, and cam/), how to write the
> Makefile? I have tried but still can not get through this, please give me a
> help!
>
Does the following example help?
S= ${.CURDIR}/../..
.PATH: $S/dev/usb $S/dev/usb2 $S/pci
KMOD= usb
SRCS= bus_if.h device_if.h usb_if.h usb_if.c \
vnode_if.h \
opt_usb.h \
hid.c hid.h usbhid.h \
usb_quirks.c ../usb/usb_quirks.h \
usb_ethersubr.c usbdevs.h \
_uhub.c \
_usb.c ../usb2/usb.h \
_usb_requests.c \
_usb_subr.c ../usb2/usb_subr.h \
_usb_transfer.c \
../usb2/usb_port.h
SRCS+= _uhci_pci.c _uhci.c ../usb2/uhci.h
SRCS+= _ohci_pci.c _ohci.c ../usb2/ohci.h
SRCS+= _ehci_pci.c _ehci.c ../usb2/ehci.h
SRCS+= opt_bus.h pci_if.h
.include
--HPS
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Someone with knowledge in VM/fork (and Copy on Write) needed
Hi, Roman (and I) need someone who is able to explain fork() and VM stuff. The problem is that the linux clone() syscall is supposed to do COW of the stack in some cases (if the child_stack argument is NULL it has to COW the thread stack, making a copy immediately is maybe ok too as a workaround). I don't know enough about the VM, so I ask here. We looked at the code of fork1(), but I can't find a description of what it is supposed to do and how flags are interpreted. Based upon the first comment in fork1() it may be able to do it itself. But this comment may also be completely unrelated to the solution we search. It would make sense to have a little bit of documentation in the vicinity of this function. So can someone explain how the stack is copied when calling fork()/fork1() or whatever_function_foo()? Bye, Alexander. -- Selling GoodYear Eagle F1 235/40ZR18, 2x 4mm + 2x 5mm, ~150 EUR you have to pick it up between Germany/Saarland and Luxembourg/Capellen http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Someone with knowledge in VM/fork (and Copy on Write) needed
Take a look at vm_forkproc in vm_glue.c -Kip On 6/8/06, Alexander Leidinger <[EMAIL PROTECTED]> wrote: Hi, Roman (and I) need someone who is able to explain fork() and VM stuff. The problem is that the linux clone() syscall is supposed to do COW of the stack in some cases (if the child_stack argument is NULL it has to COW the thread stack, making a copy immediately is maybe ok too as a workaround). I don't know enough about the VM, so I ask here. We looked at the code of fork1(), but I can't find a description of what it is supposed to do and how flags are interpreted. Based upon the first comment in fork1() it may be able to do it itself. But this comment may also be completely unrelated to the solution we search. It would make sense to have a little bit of documentation in the vicinity of this function. So can someone explain how the stack is copied when calling fork()/fork1() or whatever_function_foo()? Bye, Alexander. -- Selling GoodYear Eagle F1 235/40ZR18, 2x 4mm + 2x 5mm, ~150 EUR you have to pick it up between Germany/Saarland and Luxembourg/Capellen http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel panic 6.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeremy Baggs wrote: > Got a panic today. following are output from uname -a and kgdb,with > my kernel config as an attachment. > Looks like I had a PCI card conflicting with my SCSI controller. Sorry for the noise. Jeremy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEiNcxErogemV/I6ERArklAJ4gT3MFeQHoGOS/nImYkDBwgPLFMACdFbqk kndx+XHMlplwVgNbbGpK+7g= =936A -END PGP SIGNATURE- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
PCI Express graphics reliability/functionality in 6.1?
I'm soon to build myself a new AMD X2 workstation system on which I plan to multiboot various operating systems including FreeBSD, a couple Linux distros and probably Windows XP Pro, and probably also run virtualization software (VMWare and/or Xen.) I'm hoping for it to last me through a few years of occasional upgrades, which makes me dubious about choosing an AGP motherboard. I can't find anything specific about PCI Express in the 6.1 release notes. However, I have Googled up some reports of various PCI-E graphic cards working badly in Xorg under FreeBSD and other open source OSes. In general should PCI Express graphics cards work properly and perform reasonably well for Xorg and OpenGL graphics under FreeBSD, if I avoid the "touchier" nVidia cards, or do I need to stick with AGP for reliability? If there's a better mailing list for getting an authoritative answer to this, I'd appreciate the pointer. -- Clifton -- Clifton Royston -- [EMAIL PROTECTED] / [EMAIL PROTECTED] President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PCI Express graphics reliability/functionality in 6.1?
Clifton Royston wrote: I'm soon to build myself a new AMD X2 workstation system on which I plan to multiboot various operating systems including FreeBSD, a couple Linux distros and probably Windows XP Pro, and probably also run virtualization software (VMWare and/or Xen.) I'm hoping for it to last me through a few years of occasional upgrades, which makes me dubious about choosing an AGP motherboard. I can't find anything specific about PCI Express in the 6.1 release notes. However, I have Googled up some reports of various PCI-E graphic cards working badly in Xorg under FreeBSD and other open source OSes. In general should PCI Express graphics cards work properly and perform reasonably well for Xorg and OpenGL graphics under FreeBSD, if I avoid the "touchier" nVidia cards, or do I need to stick with AGP for reliability? I have a PCI-E nvidia card 6600 with a particular Intel board (whose numbers I don't remember right now) which used to be problematic, and generated quite a few messages on the internet to that effect. But it turned out to be a problem with the BIOS on the motherboard which was fixed when Intel came out with a BIOS upgrade. So what I am saying is that the problem might be motherboard specific rather than graphics card specific. Stephen ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PCI Express graphics reliability/functionality in 6.1?
Clifton Royston wrote: > I'm soon to build myself a new AMD X2 workstation system on which I > plan to multiboot various operating systems including FreeBSD, a couple > Linux distros and probably Windows XP Pro, and probably also run > virtualization software (VMWare and/or Xen.) I'm hoping for it to last > me through a few years of occasional upgrades, which makes me dubious > about choosing an AGP motherboard. > > I can't find anything specific about PCI Express in the 6.1 release > notes. However, I have Googled up some reports of various PCI-E > graphic cards working badly in Xorg under FreeBSD and other open source > OSes. In general should PCI Express graphics cards work properly and > perform reasonably well for Xorg and OpenGL graphics under FreeBSD, if > I avoid the "touchier" nVidia cards, or do I need to stick with AGP for > reliability? > > If there's a better mailing list for getting an authoritative answer > to this, I'd appreciate the pointer. I have an nVidia GeForce Go 7800 connected on a PCI Express 16X bus which is working very well under Xorg with FreeBSD Current and the nvidia driver from ports. It's connected to a 945PM chipset from Intel. So far it's been very stable and it's been giving me very good performances with UT2004 and Quake3. The only time I've got crashes what when I tried to use one of the raster modes on the syscon console. The system would crash trying to map the syscon framebuffer when I switched to any vt. Steph ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Someone with knowledge in VM/fork (and Copy on Write) needed
On Thu, Jun 08, 2006 at 06:53:13PM +0200, Alexander Leidinger wrote: > Hi, > > Roman (and I) need someone who is able to explain fork() and VM stuff. > > The problem is that the linux clone() syscall is supposed to do COW of > the stack in some cases (if the child_stack argument is NULL it has to > COW the thread stack, making a copy immediately is maybe ok too as a > workaround). I don't know enough about the VM, so I ask here. This is very strange behaviuor. You mean that other vm_map_entry would be shared, but stack itself becomes divorsed ? I vaguely remember some thread on linux-kernel (that got wide press coverage :)) where Linus very strong disagreed to proposal of implementing IRIX-like procs. As far as I remember, the question was exactly making the private stacks while having other vm space shared. Anyway, this looks interesting, I would like to participate :). > > We looked at the code of fork1(), but I can't find a description of > what it is supposed to do and how flags are interpreted. Based upon the > first comment in fork1() it may be able to do it itself. But this > comment may also be completely unrelated to the solution we search. Flags to fork1() are documented at man rfork(2). pgp3Nn8VazBAB.pgp Description: PGP signature
Re: working with PCI config registers (extensively)
In message: <[EMAIL PROTECTED]> Andriy Gapon <[EMAIL PROTECTED]> writes: : : I am writing a driver for some PCI hardware that does not have any IO : ports or IO memory (and thus does not have any useful BARs), but rather : it is controlled and communicated with by writes and reads of certain : vendor-specific PCI configuration registers. : : I see that I can use pci_read_config() and pci_write_config() to do : this, but I am not sure if there are any caveats that I should be aware : of, any precautions that I should take and any conventions/rules that I : should follow. : : To explain my question - I am concerned about PCI configuration space : resources ownership, concurrency, etc. Basically things that should not : matter in practice :-) The PCI bus will write to the standard TYPE 0 headers of a device on the pci bus to manage it. All other configuration registers are the responsibility of the driver. The driver can also access the registers that the pci bus manages, but care must be taken. Sounds like there'd be no conflict for you. Warner ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PCI Express graphics reliability/functionality in 6.1?
> > I can't find anything specific about PCI Express in the 6.1 release > > notes. However, I have Googled up some reports of various PCI-E > > graphic cards working badly in Xorg under FreeBSD and other open source > > OSes. In general should PCI Express graphics cards work properly and > > perform reasonably well for Xorg and OpenGL graphics under FreeBSD, if > > I avoid the "touchier" nVidia cards, or do I need to stick with AGP for > > reliability? I have a GeForce 6800GS PCIe x16 card, which has been rock-solid so far (I had to use the Nvidia drivers from ports, the 'nv' driver only gives me a messed up text console...). This is on a dual opteron 2x 846 on a Tyan Thunder K8SE motherboard. -- Rink P.W. Springer- http://rink.nu "Richter: Tribute? You steal men's souls, and make them your slaves! Dracula: Perhaps the same could be said of all religions." - Castlevania: Symphony of the Night pgpid9zKdzWmF.pgp Description: PGP signature
