Andre Oppermann wrote:
> On 12.07.2013 12:56, Fabian Keil wrote:
> > Andre Oppermann wrote:
> >
> >> On 10.07.2013 15:18, Fabian Keil wrote:
> >>> Andre Oppermann wrote:
> >> It will give a bit of debug log output which is it telling you mostly about
> >> rounding to the next nearest index va
On 12.07.2013 12:56, Fabian Keil wrote:
Andre Oppermann wrote:
On 10.07.2013 15:18, Fabian Keil wrote:
Andre Oppermann wrote:
We have a SYN cookie implementation for quite some time now but it
has some limitations with current realities for window scaling and
SACK encoding the in the few a
Andre Oppermann wrote:
> On 10.07.2013 15:18, Fabian Keil wrote:
> > Andre Oppermann wrote:
> >
> >> We have a SYN cookie implementation for quite some time now but it
> >> has some limitations with current realities for window scaling and
> >> SACK encoding the in the few available bits.
[...]
On 10.07.2013 15:18, Fabian Keil wrote:
Andre Oppermann wrote:
We have a SYN cookie implementation for quite some time now but it
has some limitations with current realities for window scaling and
SACK encoding the in the few available bits.
This patch updates and improves SYN cookies mainly
Andre Oppermann wrote:
> We have a SYN cookie implementation for quite some time now but it
> has some limitations with current realities for window scaling and
> SACK encoding the in the few available bits.
>
> This patch updates and improves SYN cookies mainly by:
>
> a) encoding of MSS, WS
We have a SYN cookie implementation for quite some time now but it
has some limitations with current realities for window scaling and
SACK encoding the in the few available bits.
This patch updates and improves SYN cookies mainly by:
a) encoding of MSS, WSCALE (window scaling) and SACK into the
On Fri, 2002-04-26 at 01:03, moto kawasaki wrote:
>
> Thank you very much, Mr. Eric Anholt,
>
> I have been testing your code on my PC, and found that kernel cannot
> initialize agpgart device so far.
The i8x0 DRM drivers require AGP to be working. I took a look at your
i830 patch today, and
OTECTED]>
From: moto kawasaki <[EMAIL PROTECTED]>
Subject: Re: DRM in the sys/ tree: looking for testers
Date: Fri, 26 Apr 2002 16:03:16 +0900 (JST)
Message-ID: <[EMAIL PROTECTED]>
kawasaki>
kawasaki> Thank you very much, Mr. Eric Anholt,
kawasaki>
kawasaki> I ha
Thank you very much, Mr. Eric Anholt,
I have been testing your code on my PC, and found that kernel cannot
initialize agpgart device so far.
Environment:
Dell Latitude C400 (w/ Intel 82830 aka I830MG)
FreeBSD 4.5 STABLE (last cvsuped around 2002/Apr/24)
XFree86 4.2.0 (using /usr/po
Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> Eric Anholt <[EMAIL PROTECTED]> writes:
> > Could people test this in-kernel DRM and tell me how it works for them?
> Seems to work fine here (trusty ol' Matrox G200 w/8 MB). Is there a
> particular DRI application I can use to somehow stress-test
On Thu, 18 Apr 2002, Brandon D. Valentine wrote:
>http://www.specbench.org/gpc/opc.static/vp50.htm
This is probably a more useful URL:
http://www.specbench.org/gpc/opc.static/overview.htm
(thought I hit back before copying-and-pasting the URL, but I guess not)
- Brandon D. Valentine
To Unsu
>
> Could people test this in-kernel DRM and tell me how it works
> for them?
Works fine for me on a Matrox G400 with the standard Mesa apps, Linux Unreal
Tournament, and a custom build of Quake2 for FreeBSD. Good work!
Scott
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
On 18 Apr 2002, Dag-Erling Smorgrav wrote:
>Eric Anholt <[EMAIL PROTECTED]> writes:
>> Could people test this in-kernel DRM and tell me how it works for them?
>
>Seems to work fine here (trusty ol' Matrox G200 w/8 MB). Is there a
>particular DRI application I can use to somehow stress-test or
>b
Eric Anholt <[EMAIL PROTECTED]> writes:
> Could people test this in-kernel DRM and tell me how it works for them?
Seems to work fine here (trusty ol' Matrox G200 w/8 MB). Is there a
particular DRI application I can use to somehow stress-test or
benchmark the module? I've gotten kind of tired of
The DRM kernel modules (kernel support for 3d hardware acceleration
through the DRI) may be integrated into our sys tree soon. I may be
getting a commit bit soon to work on this. I think getting the modules
in the sys tree will help keep the DRI supported on FreeBSD even if I
become less active,
On Thu, Jun 01, 2000 at 04:32:42PM -0700, Bill Paul wrote:
> > > - It has a 21143 chip
> >
> > Well, the de driver says 21142. The dc driver says 21143.
>
> It's just a difference in chip revision, really.
OK.
> > This one does not have AUI so that is not going to be a problem. What I do
> >
On Fri, Jun 02, 2000 at 12:30:13AM -0700, Bill Paul wrote:
> >
> > For reference the ID reported is:
> >
> > de0@pci0:3:0: class=0x02 card=0x chip=0x00191011 rev=0x11 hdr=0x00
>
> Hm, ok. First of all, I made a mistake in what I told you. The code in
> dcphy.c checks the subsystem
>
> For reference the ID reported is:
>
> de0@pci0:3:0: class=0x02 card=0x chip=0x00191011 rev=0x11 hdr=0x00
Hm, ok. First of all, I made a mistake in what I told you. The code in
dcphy.c checks the subsystem ID, not the device ID. The device ID is always
the same, since that ident
> > - There's one interface involved here
>
> Correct.
>
> > - It has a 21143 chip
>
> Well, the de driver says 21142. The dc driver says 21143.
It's just a difference in chip revision, really.
> This one does not have AUI so that is not going to be a problem. What I do
> wonder, though, is
On Thu, Jun 01, 2000 at 12:51:25PM -0700, Bill Paul wrote:
> > Hi Bill,
> >
> > I applied your patches to -current without incidents.
> >
> > I have a testbox (Digital dual P6) that gives:
> >
> > May 31 10:56:38 p6 /kernel: dc0: port
> [...]
> > May 31 11:03:27 p6 /kernel: dc0: watchdog tim
> Hi Bill,
>
> I applied your patches to -current without incidents.
>
> I have a testbox (Digital dual P6) that gives:
>
> May 31 10:56:38 p6 /kernel: dc0: port
[...]
> May 31 11:03:27 p6 /kernel: dc0: watchdog timeout
>
> This box can also house an Alpha Miata MX5 mainboard, the Intel & A
On Wed, May 31, 2000 at 12:30:51PM +0200, Wilko Bulte wrote:
> On Tue, May 30, 2000 at 09:29:46AM -0700, Bill Paul wrote:
> > > On Tue, May 30, 2000 at 12:28:25AM -0700, Bill Paul wrote:
> > > > Several people have reported problems with if_dc botching autonegotiation
> > > > on 21143 NICs with no
On Wed, May 31, 2000 at 12:30:51PM +0200, Wilko Bulte wrote:
> On Tue, May 30, 2000 at 09:29:46AM -0700, Bill Paul wrote:
> May 31 10:56:38 p6 /kernel: dc0: port
> 0xec00-0xec7f m
> em 0xfdfffc00-0xfdfffc7f irq 9 at device 3.0 on pci0
> May 31 10:56:38 p6 /kernel: dc0: Ethernet address: 00:00:f8:
Just to see if if_dc has kept working on a machine that had it working
before (Alpha Miata GL): works just fine with the patches applied.
Wilko
[goes back to digging up the Miata MX5]
--
Wilko Bulte FreeBSD, the power to serve http://www.freebsd.org
To Unsubscribe: send mail to [EMAIL
On Tue, May 30, 2000 at 09:29:46AM -0700, Bill Paul wrote:
> > On Tue, May 30, 2000 at 12:28:25AM -0700, Bill Paul wrote:
> > > Several people have reported problems with if_dc botching autonegotiation
> > > on 21143 NICs with non-MII media, such as the DEC/Compaq DE500-BA and
> > > the built-in 1
In article <[EMAIL PROTECTED]>,
Bill Paul <[EMAIL PROTECTED]> wrote:
> Several people have reported problems with if_dc botching autonegotiation
> on 21143 NICs with non-MII media, such as the DEC/Compaq DE500-BA and
> the built-in 10/100 ethernet on some alphas. As my first official act
> as a BS
> On Tue, May 30, 2000 at 12:28:25AM -0700, Bill Paul wrote:
> > Several people have reported problems with if_dc botching autonegotiation
> > on 21143 NICs with non-MII media, such as the DEC/Compaq DE500-BA and
> > the built-in 10/100 ethernet on some alphas. As my first official act
> > as a BS
On Tue, May 30, 2000 at 12:28:25AM -0700, Bill Paul wrote:
> Several people have reported problems with if_dc botching autonegotiation
> on 21143 NICs with non-MII media, such as the DEC/Compaq DE500-BA and
> the built-in 10/100 ethernet on some alphas. As my first official act
> as a BSDi/WC empl
Several people have reported problems with if_dc botching autonegotiation
on 21143 NICs with non-MII media, such as the DEC/Compaq DE500-BA and
the built-in 10/100 ethernet on some alphas. As my first official act
as a BSDi/WC employee, I sat down and tried to fix this. I produced
some patches for
> if they used an MII transceiver, then it should work okay, but if
> not you could be in for trouble. I wish I didn't have to say that,
> but I just don't have the hardware to test with.
You know what I tell people who use that excuse... ;)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECT
empting to combine support
> > for several tulip like chipsets into a single driver in an attempt to
> > reduce code bloat. I've gotten things to where I think they work okay,
> > but I'm looking for testers who have FreeBSD-current running with the
> > followi
t. I've gotten things to where I think they work okay,
> but I'm looking for testers who have FreeBSD-current running with the
> following PCI chipsets:
YES! Hurray! You are my hero! I have been suffering under the
if_de driver which utterly fails to grok 100Mb full duplex
k they work okay,
but I'm looking for testers who have FreeBSD-current running with the
following PCI chipsets:
- Macronix 98713, 98713A, 98715A or 98725 (NDC sohoware, CNet)
- Davicom DM9102 (Jaton XpressNet)
- ASIX AX88140A or AX88141 (CNet)
- ADMtek AL981 Comet or AN985 Centaur
- Lite-On
33 matches
Mail list logo
