On Thu, 09 Nov 2000 at 13:26:09 -0700, Justin T. Gibbs wrote:
> As some of you may know, I'm working on a 501(c)3 (tax exempt/non-profit)
> determination for the FreeBSD Foundation. The IRS seems to be a little
> confused about the nature of FreeBSD and we're currenlty working on
> a response to
Tony Finch writes:
> >So.. what stuff in /home/cvs/CVSROOT can I change so that sources
> >in freebsd/* get $FreeBSD$ substitution, but other sources get the
> >normal $Id$ substitution? Surely someone has solved this already.. ?
>
> If you are using the FreeBSD version of CVS (which has been pat
Archie Cobbs <[EMAIL PROTECTED]> wrote:
>
>So.. what stuff in /home/cvs/CVSROOT can I change so that sources
>in freebsd/* get $FreeBSD$ substitution, but other sources get the
>normal $Id$ substitution? Surely someone has solved this already.. ?
If you are using the FreeBSD version of CVS (which
Archie Cobbs <[EMAIL PROTECTED]> wrote:
> even worse, mergemaster in some cases seems to be comparing only
> the $FreeBSD$ strings and incorrectly concluding that certain
> files don't need upgrading, when in fact they do.
If the -s switch isn't specified, mergemaster compares id strings
first,
I havn't said this for a while. However, I frequently think it.
I just cvsup'd, make world, make and install a new kernel. All
without a hitch.
Good Work Developers.
Thanks,
tomdean
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, 9 Nov 2000, Warner Losh wrote:
> I think you are right. Even if the emulator ws there, it was only
> used to run the ROM post code, not to be active any time after the
> boot to use at randomly...
I looked at the NetBSD/Alpha EISA code. Looks like that does everything
we'll need.
--
|
Hi everybody!
I can see no one has reported these recently so I will...
After I successfully made the buildworld, I proceeded to make buildkernel.
However, the makedep did not go through. It is because Marcel introduced a
new method of getting linux_sysent.c linux_syscall.h and linux_proto.h (th
> At one (gross) time in history, Alphas included an x86 emulator
> in ROM to facilitate this (and other BIOS POST initialization stuff,
> mostly).
They still do.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because peo
> Timesharing requires co-operation from both device and bus, but this
> is a completely different issue. No drivers currently support
> timesharing. `sio' at a minimum probably should, as it was the
> motivating example for adding that feature. (My laptop has three PnP
> sio ports: an internal
In message <[EMAIL PROTECTED]> "Matthew N.
Dodd" writes:
: On Thu, 9 Nov 2000, Terry Lambert wrote:
: > At one (gross) time in history, Alphas included an x86 emulator in ROM
: > to facilitate this (and other BIOS POST initialization stuff, mostly).
:
: Somehow I doubt I'll be able to make VM86
On Thu, 9 Nov 2000, Terry Lambert wrote:
> At one (gross) time in history, Alphas included an x86 emulator in ROM
> to facilitate this (and other BIOS POST initialization stuff, mostly).
Somehow I doubt I'll be able to make VM86 calls to BIOS interrupt services
on the Alpha.
--
| Matthew N. Dod
>I'm subscribed to -stable and not current, and yet I received this
>email. Do the lists get mixed up once in a while?
You're the victim of mh's dist command which I used to make this
plea to several mailing lists. Unfortunately it looks like
cross posting is disabled in majordomo (probably for
I'm subscribed to -stable and not current, and yet I received this
email. Do the lists get mixed up once in a while?
- Donn
On Thu, 9 Nov 2000, Justin T. Gibbs wrote:
> As some of you may know, I'm working on a 501(c)3 (tax exempt/non-profit)
> determination for the FreeBSD Foundation. The IR
As some of you may know, I'm working on a 501(c)3 (tax exempt/non-profit)
determination for the FreeBSD Foundation. The IRS seems to be a little
confused about the nature of FreeBSD and we're currenlty working on
a response to an initial determination from the IRS that was not
favorable. One thi
Now that someone has implementented resource alignment in the resource
allocator, someone could review and integrate the attached patch.
Background:
I do have an old system with several PnP devices. Two of the request the
following IO ports:
first device: port range 0x100-0x3ff size=1 align=1
se
> >As a backgrounder for other-than-Justin, Adaptec has a habit of
> >making multipurpose ROMs that sit on different types of devices,
> >so that they don't have to maintain multiple images. It's the
> >EISA stuff in these ROMs that causes a non-EISA BIOS based EISA
> >probe to incorrectly identi
>
>How do we use the EISA BIOS on an Alpha or an SGI though?
I believe thorpej recently committed some code in NetBSD to do this
on the Alpha.
--
Justin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
>> >What about EISA/VL or EISA/PCI systems?
>>
>> What about them? PCI devices are supposed to be found via PCI configuration
>> space access. Even in these machines where a PCI card can be falsly
>> probed as an EISA card, the standard PCI configuration mechanism works
>> to correctly find PCI
> > (I can't remember how, but the EISA BIOS knew not to treat these as
> > EISA cards).
>
> Because the EISA Config Util. saves the config to the system NVRAM which
> the EISA BIOS reads to get the configuration.
Yes, that was how, thanks for jogging my memory...
> Using the EISA BIOS stuff mi
> >What about EISA/VL or EISA/PCI systems?
>
> What about them? PCI devices are supposed to be found via PCI configuration
> space access. Even in these machines where a PCI card can be falsly
> probed as an EISA card, the standard PCI configuration mechanism works
> to correctly find PCI devic
On Thu, 9 Nov 2000, Terry Lambert wrote:
> (I can't remember how, but the EISA BIOS knew not to treat these as
> EISA cards).
Because the EISA Config Util. saves the config to the system NVRAM which
the EISA BIOS reads to get the configuration.
Using the EISA BIOS stuff might be the way to go.
> >Humm... I had wondered why that was there. Is there a way to detect VLB
> >devices some other way?
>
> This is specific to the aha2842 and is the only way I know of detecting
> those boards.
I thought that there was a tricky way, which involved doing
the EISA non-destructive card identifica
Point taken, however; does it not allowe the services to be configured by such things
as ip, and time period
and offer yet better activity logging? With the approriate firewall setup the added
layers are worth the
trouble.
Well enough b/w wasted on this for now.
m
Neil Blakey-Milner wrote:
< said:
> - pci drivers "know" that pci interrupts are shareable and force
> RF_SHAREABLE. Is this required by the pci spec?
Yes.
> - the isa compatibility code and pcvt force RF_SHAREABLE although isa
> irqs are rarely shareable.
This is a bug. I suspect it may be due to code rot, relat
I'm trying to reinstall 486sx win 3.0 dos 6.2. I keep getting message error
unable to control a20 line xms driver not installed please help.
--- Rafael Cruz
--- [EMAIL PROTECTED]
--- EarthLink: It's your Internet.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-curre
>
>What about EISA/VL or EISA/PCI systems?
>
What about them? PCI devices are supposed to be found via PCI configuration
space access. Even in these machines where a PCI card can be falsly
probed as an EISA card, the standard PCI configuration mechanism works
to correctly find PCI devices. VL
On Thu, 9 Nov 2000, Justin T. Gibbs wrote:
> You'll fail the attach because the ID is not in the table of known
> EISA IDs. Joerg can probably give additional examples of this
> problem. This is one reason we don't probe all 15 slots yet. If we
> reserved the address space properly before doing
>>What machine and what does the output from the probe/attach look like?
>
>You'll fail the attach because the ID is not in the table of known
>EISA IDs.
I forgot to mention that the probe will cause the aic78XX controller
to get very upset as you end up referencing a register that should
only be
>On Thu, 9 Nov 2000, Peter Wemm wrote:
>> Do you want to know what is even funnier? One of my onboard ahc *PCI*
>> controllers (7895 based I think) also responds to the EISA probes if I
>> enable EISA.
>
>What machine and what does the output from the probe/attach look like?
You'll fail the atta
On Tue, Nov 07, 2000 at 02:29:40AM -0600, Michael C . Wu wrote:
> On Tue, Nov 07, 2000 at 04:13:37PM +0800, Clive Lin scribbled:
> | may panic because of several IPFIREWALL options. The panic message I could
> | tell is about trap 12, swi6: clock and page fault. And the machine hangs
> | solidly r
On Wed, 8 Nov 2000, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> "Matthew N.
>Dodd" writes:
> : On Wed, 8 Nov 2000, Warner Losh wrote:
> : > The cardbus code, for example, will or in the RF_SHAREABLE bit when
> : > appropriate.
> :
> : Right, but the drivers that are consumers of the PCI
31 matches
Mail list logo
