On Sun, Mar 26, 2000 at 11:04:35PM -0500, John Von Essen wrote:
> What is the status of support for onboard Intel networking? Intel
> EtherExpress PRO/100 PCI Cards work fine with the fxp0 driver, but I am
> have having alot of problems with the onboard intel networking. For
> example, SuperMicro
Hi,
I heard that bochs (ports/emulators/bochs) gets now LGPLed, so I tryed
to run FreeBSD-CURRENT on bochs VM,then I got two problems.
1.ISA PnP module try to read 0x??3 address. and Virtual VGA controller
in bochs does not accept to read on 0x3e3 then the bochs VM panics.
2.ATA driver always
On Sun, Mar 26, 2000 at 10:42:40PM -0700, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Nikolai Saoukh writes:
> : I was wrong. 'unknown' driver attaches with (-100) priority.
> : I have another problem -- when 'unknown' driver attached
> : to my device, my kldloaded driver is not called at
In message <[EMAIL PROTECTED]> Nikolai Saoukh writes:
: I was wrong. 'unknown' driver attaches with (-100) priority.
: I have another problem -- when 'unknown' driver attached
: to my device, my kldloaded driver is not called at all, so I can't
: override 'unknown' with higher priority. So for a w
On Sun, Mar 26, 2000 at 10:30:48PM -0700, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Nikolai Saoukh writes:
> : Current 'unknown' driver attaches with 0 priority, thus kldloaded
> : driver is not called at all. And even when 'unknown' driver attaches
> : with very low priority, what hap
In message <[EMAIL PROTECTED]> Nikolai Saoukh writes:
: Current 'unknown' driver attaches with 0 priority, thus kldloaded
: driver is not called at all. And even when 'unknown' driver attaches
: with very low priority, what happens when real driver will be
: kldunloaded?
Hmmm. The unknown driver
On Sun, Mar 26, 2000 at 10:18:49PM -0700, Warner Losh wrote:
> : No good, because with current 'unknown' driver any kldloadable
> : driver for pnp device would not get its resources.
>
> In theory, if one matches with a -1 or smaller rather than 0, then it
> will be detached on reprobe. Isn't t
In message <[EMAIL PROTECTED]> Nikolai Saoukh writes:
: On Sun, Mar 26, 2000 at 04:40:53PM -0700, Warner Losh wrote:
:
: > First, I'll create a null driver. Let's call it "null" since
: > "resourceplaceholder" is too long. This driver's probe routine would
: > always succeed, and its attach rou
On Sun, Mar 26, 2000 at 04:40:53PM -0700, Warner Losh wrote:
> First, I'll create a null driver. Let's call it "null" since
> "resourceplaceholder" is too long. This driver's probe routine would
> always succeed, and its attach routine would gobble up all the
> resources associated with this.
> In message <[EMAIL PROTECTED]> FreeBSD MAIL writes:
> : current /root 78% pccardd -f /etc/pccard.conf.sample
> : current /root 79% Mar 27 01:27:20 current pccardd[215]: No card in database for
>""("")
> : Mar 27 01:27:20 current pccardd[215]: No card in database for ""("")
>
> This tells me t
What is the status of support for onboard Intel networking? Intel
EtherExpress PRO/100 PCI Cards work fine with the fxp0 driver, but I am
have having alot of problems with the onboard intel networking. For
example, SuperMicro PIIIDM3 motherboards, while setting up a firewall
server, I get "Unsuppo
> Hmm. So I've compiled the TenDRA port, and I'm toying around with it,
> trying to get it to compile Qt (and perhaps gnu's libstdc++), but not
> suprisingly it seems to dislike some of the more basic (QList and QString
> and other template stuff) code in Qt, meaning even something as simple as
>
In message <[EMAIL PROTECTED]> FreeBSD MAIL writes:
: current /root 78% pccardd -f /etc/pccard.conf.sample
: current /root 79% Mar 27 01:27:20 current pccardd[215]: No card in database for
:""("")
: Mar 27 01:27:20 current pccardd[215]: No card in database for ""("")
This tells me that the card
Hmm. So I've compiled the TenDRA port, and I'm toying around with it,
trying to get it to compile Qt (and perhaps gnu's libstdc++), but not
suprisingly it seems to dislike some of the more basic (QList and QString
and other template stuff) code in Qt, meaning even something as simple as
moc can't
I am using a WavLAN ISA adaptor.. it comes up as
pcic0: at port 0x3e2 iomem 0xd irq 10 on isa0
pcic0: management irq 10
pccard0: on pcic0
pccard1: on pcic0
have it set in the kernel as.
device pcic0 at isa? irq 10 port 0x3e2 iomem 0xd
I have also tired
device
In message <[EMAIL PROTECTED]> Jeroen Ruigrok/Asmodai
writes:
: I assume you mean PCI devices, since ISA are detailed in:
:
: /src/sys/i386/isa/isa_compat.h
Yes. However, the #error should be in ISA too since it is a common
pilot error, despite having an UPDATING entry for a while.
Warner
T
[[ moved from stable to hackers ]]
dodd> Ah. So what we really want is some mechanism to tell the kernel 'hey,
dodd> you! don't use this ioport/irq whatever.' (or otherwise mark some
dodd> resources as not being available to PnP devices.)
imp> I think that a null driver could easily be written
Keri Carpenter wrote:
>
> sourceXchange is looking for a few good device driver developers!
>
> We are sending out this targeted email only to those developers who
> have identified an interest in device drivers through the skills
> listed in your technical profile on sourceXchange.
>
> Here's
On Sun, 26 Mar 2000, Arun Sharma wrote:
> On Sun, Mar 26, 2000 at 11:04:08AM -0600, Richard Seaman, Jr. wrote:
> > No. See the file libc_thread.c in the linuxthreads port.
> >
> > Note that if you call rfork (RF_MEM...) without any supporting
> > infrastructure (eg. as provided by the linuxthre
Me and my roommate saw a similar thing occuring when developing a Windows
NT EventLog -> syslogd forwarder (http://www.schizo.com/software/sislog/)
on an older 4.0-CURRENT machine and a 2.2.8-RELEASE machine..
We concluded that it appears to be if the host sending the syslog messages
is unresolv
On Sun, Mar 26, 2000 at 11:04:08AM -0600, Richard Seaman, Jr. wrote:
> No. See the file libc_thread.c in the linuxthreads port.
>
> Note that if you call rfork (RF_MEM...) without any supporting
> infrastructure (eg. as provided by the linuxthreads port) you
> are in dangerous territory. You do
On Sat, Mar 25, 2000 at 10:56:15PM -0800, Arun Sharma wrote:
> When I try to compile a simple multi threaded program using a wrapper
> around rfork (from linuxthreads port), I get the following core dump:
>
> ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:54
>
> Investigation
On Sat, Mar 25, 2000 at 10:36:24PM -0600, Jonathan Lemon wrote:
> On Sat, Mar 25, 2000 at 09:25:33PM -0500, Keith Stevenson wrote:
> >
> > Which card(s) do your patches support? I have a 3Com 3CR990-TX (typhoon)
> > which does both TCP checksumming and 3DES (for IPSec). I'd love to give
> > it
-On [2326 00:00], Warner Losh ([EMAIL PROTECTED]) wrote:
>
>However, I was thinking that it would be nice if there was something
>simple to grep for to see what drivers still needed to be converted.
I assume you mean PCI devices, since ISA are detailed in:
/src/sys/i386/isa/isa
Dear every FreeBSD experts,
I was referrred from Joerg Wunsch that some of you may be interested in
a project of setting up Virtual Machine on Intel FreeBSD platform.
We are a startup web hosting company in Hong Kong and China. We are keen
to develop a system which is capable of running multiple
subscribe freebsd-hackers
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
26 matches
Mail list logo
