On Thu, Jun 02, 2011 at 10:49:43PM +0100, Owain Ainsworth wrote:
> Been running with this for a couple of weeks, seems to work fine.
>
> ok?
>
> diff --git dev/pci/if_iwn.c dev/pci/if_iwn.c
> index 16765f4..a54556b 100644
> --- dev/pci/if_iwn.c
> +++ dev/pci/if_iwn.c
> @@ -338,7 +338,8 @@ iwn_att
2 usersLoad 0.09 0.09 0.08 Thu Jun 2 20:12:59 2011
DEVICE READWRITE RTPS WTPS SECSTATS
sd0 0000 0.0 588656
numbufs
sd1 0000
> Date: Thu, 2 Jun 2011 22:49:43 +0100
> From: Owain Ainsworth
>
> Been running with this for a couple of weeks, seems to work fine.
>
> ok?
>
> diff --git dev/pci/if_iwn.c dev/pci/if_iwn.c
> index 16765f4..a54556b 100644
> --- dev/pci/if_iwn.c
> +++ dev/pci/if_iwn.c
> @@ -338,7 +338,8 @@ iwn_a
Been running with this for a couple of weeks, seems to work fine.
ok?
diff --git dev/pci/if_iwn.c dev/pci/if_iwn.c
index 16765f4..a54556b 100644
--- dev/pci/if_iwn.c
+++ dev/pci/if_iwn.c
@@ -338,7 +338,8 @@ iwn_attach(struct device *parent, struct device *self, void
*aux)
}
/*
> From: Brad
> Date: Thu, 02 Jun 2011 14:29:52 -0400
>
> - Original message -
> > In the spirit of trying to enable MSI for various devices, who wants
> > to play with bge(4)?
> >
> > bge0 at pci2 dev 0 function 0 "Broadcom BCM5761" rev 0x10, BCM5761 A1
> > (0x5761100): msi, address 00:1
On Thu, Jun 02, 2011 at 08:25:23PM +0200, Michael Knudsen wrote:
| I enabled MSI for the wpi(4) in my X60:
|
| wpi0 at pci2 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02: msi,
MoW2, address 00:13:02:9b:f4:89
|
| It didn't blow up right away. Anyone else feel lucky?
Seems like my Z61m
> Date: Thu, 2 Jun 2011 20:25:23 +0200
> From: Michael Knudsen
>
> I enabled MSI for the wpi(4) in my X60:
>
> wpi0 at pci2 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02: msi,
> MoW2, address 00:13:02:9b:f4:89
>
> It didn't blow up right away. Anyone else feel lucky?
Reasonably conf
- Original message -
> In the spirit of trying to enable MSI for various devices, who wants
> to play with bge(4)?
>
> bge0 at pci2 dev 0 function 0 "Broadcom BCM5761" rev 0x10, BCM5761 A1
> (0x5761100): msi, address 00:10:18:4b:23:b4 brgphy0 at bge0 phy 1:
> BCM5761 10/100/1000baseT PHY,
I enabled MSI for the wpi(4) in my X60:
wpi0 at pci2 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02: msi, MoW2,
address 00:13:02:9b:f4:89
It didn't blow up right away. Anyone else feel lucky?
Index: if_wpi.c
===
RCS file:
In the spirit of trying to enable MSI for various devices, who wants
to play with bge(4)?
bge0 at pci2 dev 0 function 0 "Broadcom BCM5761" rev 0x10, BCM5761 A1
(0x5761100): msi, address 00:10:18:4b:23:b4
brgphy0 at bge0 phy 1: BCM5761 10/100/1000baseT PHY, rev. 0
Works for me so far.
Index: if
On Thu, Jun 2, 2011 at 8:52 AM, Paul Irofti wrote:
> Any objections to adding this to the LIST structure?
Yes, because it doesn't work.
If you want that, just change it from a LIST to a TAILQ.
Philip Guenther
Any objections to adding this to the LIST structure?
I needed this a bounch of times and I think it makes sense in a *doubly*
linked list.
Index: sys/sys/queue.h
===
RCS file: /cvs/src/sys/sys/queue.h,v
retrieving revision 1.32
diff
Hi,
Removing unused code:
* arch/mac68k/include/keyboard.h not used in kernel sources
* not need define KEYBOARD_ARRAY (variable keyboard[] used only in
dev/adb/akbd.c if defined WSDISPLAY_COMPAT_RAWKBD)
OK ?
--
Alexandr Shadchin
Index: arch/mac68k/include/keyboard.h
Conozca como la Nueva Red Social Mercosur.com puede trabajar para Ud
> Date: Wed, 1 Jun 2011 23:13:04 -0400
> From: Kenneth R Westerback
>
> Try msi and fallback to old intr mapping. Works on my box where the
> ahci is on a non-msi bus.
In other words; ou didn't really test this ;)
> ok?
No. I've looked at the Linux code, and their code suggests there are
some
On Wed, Jun 01, 2011 at 11:13:04PM -0400, Kenneth R Westerback wrote:
| Try msi and fallback to old intr mapping. Works on my box where the
| ahci is on a non-msi bus.
I have the exact same 82801GBM controller as mk in a Lenovo Z61m.
Works fine here too, the dmesg line shows 'msi' and I've not not
Hi,
Recently it came to my attention that date(1) on solaris
doesn't quite work the way I expected it to. Specifically,
the result of `date +%s' was unexpected.
I soon came to the realization that OpenBSD's man page for
date(1) lies a bit about POSIX compliance and omits the
+format conversion sp
On Wed, Jun 01, 2011 at 11:13:04PM -0400, Kenneth R Westerback wrote:
> Try msi and fallback to old intr mapping. Works on my box where the
> ahci is on a non-msi bus.
Works on my X60 which has ahci on an msi bus:
luggage$ dmesg | grep ^ahci
ahci0 at pci0 dev 31 function 2 "Intel 82801GBM AHCI" r
18 matches
Mail list logo