Nicolas Souchu writes:
<...>
> What is the hose field?
It is for server-class alphas. Alphas do their peer PCI buses a
little differently. Rather than have a ppb between "peer" pci buses,
each different peer bus (or hose) is rooted separately at the nexus.
So you can have two PCI buses labele
I'm going to try these ideas out, thanks for the pointers. I'm
highly motivated to stop waiting so long :-). And a nice
use for the systems that have been piling up, if this works
out.
I'll be reporting back...
Cheers,
Russell
%
%On 20-Jan-01 Wes Peters wrote:
%> "Russell L. Carter" wrote:
Thanks for clearing that one up :) I feel a lot better now :)
Now - do you understand why Nicolas' code always returns 0x6? ;-)
On Sat, Jan 20, 2001 at 04:35:11PM -0800, John Baldwin wrote:
> Look in /sys/compile/ after compiling a kernel, it should be in pci_if.*
> It's a function that ues ko
On 21-Jan-01 Donald J . Maddox wrote:
> Heh, this is pretty wierd :)
>
> I was intrigued by your little problem, so I started looking around.
> In sys/dev/pci/pciar.h is:
>
> static __inline u_int32_t
> pci_read_config(device_t dev, int reg, int width)
> {
> return PCI_READ_CONFIG(device_ge
Heh, this is pretty wierd :)
I was intrigued by your little problem, so I started looking around.
In sys/dev/pci/pciar.h is:
static __inline u_int32_t
pci_read_config(device_t dev, int reg, int width)
{
return PCI_READ_CONFIG(device_get_parent(dev), dev, reg, width);
}
However, this is the
On 20-Jan-01 Wes Peters wrote:
> "Russell L. Carter" wrote:
>> %See the paper "Recursive Make Considered Harmful." Make is an amazing
>> %tool when used correctly.
>>
>> That's not the problem, unfortunately. I've never had a problem
>> rebuilding dependencies unnecessarily, or any of those
Hello, this is an automated message from another.com.
We have tried to send your email to the address below, but we cannot find a
user with that address. Please check the address of the person you are
emailing and try again.
[EMAIL PROTECTED]
If you need further help, email us at [EMAIL PROTECTE
On Sat, Jan 20, 2001 at 04:18:35PM +0100, Nicolas Souchu wrote:
> Hi folks,
>
> I have a problem with R4.2. The device driver I'm currently
> writing can't retrieve correctly the value from a PCI configuration
> register. What is strange is that when using the pciconf tool I get
> the result I ex
On Sat 2001-01-20 (16:39), Sergey Babkin wrote:
> All,
>
> I've committed these changes for cron to support DST change
> to -current (see PR bin/24494 for description of my tests).
> Everyone is welcome to test them out.
> Please let me know if you encounter any problems caused by them
> (and bet
All,
I've committed these changes for cron to support DST change
to -current (see PR bin/24494 for description of my tests).
Everyone is welcome to test them out.
Please let me know if you encounter any problems caused by them
(and better do that before these changes would be MFCed to -stable
in
> I think this is a BIOS issue. I don't think any BIOS will let you
> boot from arbitrarily-formatted floppies :)
the 1480 format works.
luigi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
"Russell L. Carter" wrote:
>
> %> No it would not! Back in '94 I ported dmake to FreeBSD
> %> and built just about every numerics package out there
> %> on a 4 CPU cluster. Worked fine, but not much in overall
> %> speedup, because... tadum! Where do you get the source
> %> files, and how do yo
On Wed, Jan 17, 2001 at 18:48 +0100, Gerhard Sittig wrote:
>
> I'm just editing the PR with the cron patches [ ... ]
So it finally happened. It's filed as "bin/24485: [PATCH] to
make cron(8) handle clock jumps" and got archived at
http://www.freebsd.org/cgi/query-pr.cgi?pr=24485
I don't see it
I don't know where you came across a 2.88M fixit.flp... But, if
you go to your friendly local ftp.freebsd.org mirror and look for:
pub/FreeBSD/releases/i386/4.2-RELEASE/floppies/fixit.flp
You will find a 1.44M version :)
On Sat, Jan 20, 2001 at 01:02:16PM -0500, rt wrote:
>
> i am havin
i am having trouble building a fixit floppy - which is
2.88 M image. i can perform:
dd if=fixit.flp of=/dev/fd0c (on my openbsd box)
but it reaches the end of the device, writing 1.44 (obviously).
when i try to use this disk, it looks like it works, but
I think this is a BIOS issue. I don't think any BIOS will let you
boot from arbitrarily-formatted floppies :)
On Sat, Jan 20, 2001 at 08:24:05PM +0900, [EMAIL PROTECTED] wrote:
> Dear sirs
>
> I have been developing many kinds of 1FD-applications(
> http://www.ryuchi.org/~iloved ) with FreeBSD
Hi folks,
I have a problem with R4.2. The device driver I'm currently
writing can't retrieve correctly the value from a PCI configuration
register. What is strange is that when using the pciconf tool I get
the result I expect, not with pci_read_config().
pciconf -r pci0:7:3: 0x48 returns 0x000
On Fri, Jan 12, 2001 at 10:41:29AM +, Nick Hibma wrote:
>
>
> You've been speaking to Nicolas Souchu, right? He has written the
> current driver and seems to know a fair bit about this topic.
We've solved the problem.
>
> Nick
>
> > | I'll put this on my pile of things to and dig through
"Crist J. Clark" <[EMAIL PROTECTED]> writes:
> On Sat, Jan 20, 2001 at 01:51:43AM +0100, Dag-Erling Smorgrav wrote:
> > Chris Stenton <[EMAIL PROTECTED]> writes:
> > > Fatal server error:
> > > xf86OpenConsole: Server must be suid root
> >
> > This is yo
Dear sirs
I have been developing many kinds of 1FD-applications(
http://www.ryuchi.org/~iloved ) with FreeBSD2.2.8.
1FD-SQUID, 1FD-SAMBA, etc.
Recently, I can use fd0.1720( 21 Sectors/track, 82 track), not fd0.1440(18
Sectors/track, 80 track).
But, fd0.1720 cannot be bootable.
I can see "boo
On Sat, Jan 20, 2001 at 01:51:43AM +0100, Dag-Erling Smorgrav wrote:
> Chris Stenton <[EMAIL PROTECTED]> writes:
> > Fatal server error:
> > xf86OpenConsole: Server must be suid root
>
> This is your clue.
He might also be running at elevated secureleve
On Fri 2001-01-19 (12:44), Matt Dillon wrote:
> :I'm just editing the PR with the cron patches to "catch up" with
> :OpenBSD in this respect (stating that it doesn't handle DST, but
> :has benefits whenever one's clock is jumping or cron waking up
> :too late and _could_ be extended to handle DST)
22 matches
Mail list logo
