Pyun YongHyeon wrote:
It may still have some odd cases for dual port controllers. I guess
the reset sequence of the controller is important as status LEs are
shared between ports. The patch you tried in previous patch(
msk.88E8040.patch5) has a couple of fixes which might also help to
stability u
On Mon, Jul 07, 2008 at 08:43:59PM +0200, Krzysztof J??druczyk wrote:
> Pyun YongHyeon wrote:
> >Since the patch had lots of code not related with 88E8062 dual port
> >controller, would you try attached patch again? I think the attached
> >patch is minimal one that makes 88E8062 work.
> >
> >
Pyun YongHyeon wrote:
Since the patch had lots of code not related with 88E8062 dual port
controller, would you try attached patch again? I think the attached
patch is minimal one that makes 88E8062 work.
The patch also try to enable MSI for dual port controllers. At the
time of writing support
On Sun, Jul 06, 2008 at 10:45:28PM +0200, Krzysztof J??druczyk wrote:
> Pyun YongHyeon pisze:
> >
> >Would you try the patch at the following URL?
> >http://people.freebsd.org/~yongari/msk/msk.88E8040.patch5
> >
> >The diff generated against HEAD and it could be cleanly applied to
> >7-stabl
Pyun YongHyeon pisze:
Would you try the patch at the following URL?
http://people.freebsd.org/~yongari/msk/msk.88E8040.patch5
The diff generated against HEAD and it could be cleanly applied to
7-stable. 7-stable also has a couple of important bug fixes.
So it would be better to use 7-stable.
On Thu, Jul 03, 2008 at 01:25:29AM +0200, Krzysztof J?druczyk wrote:
> Pyun YongHyeon pisze:
> > Would you try attached patch?
> >The patch is just for checking code path of fiber media.
>
> It's slightly better - some media gets detected, but looks weird to me
> (and doesn't communicate w
Pyun YongHyeon pisze:
> Would you try attached patch?
The patch is just for checking code path of fiber media.
It's slightly better - some media gets detected, but looks weird to me
(and doesn't communicate with other machines on the switch):
# ifconfig
msk0: flags=8802 metric 0 mtu 1500
On Tue, Jul 01, 2008 at 12:32:04PM +0200, Krzysztof J??druczyk wrote:
> Hi,
>
> Pyun YongHyeon wrote:
> >The 88E8062 support wasn't tested due to lack of hardware and I just
> >copied the device id from myk driver. Would you show me the output
> >of "devinfo -rv| grep oui" ? Also it would be
,--[ On Mon, Jun 30, 2008 at 01:54:23PM +0200, Krzysztof Jedruczyk wrote:
| Hi,
|
| I am trying to bring up gigabit interface in couple of Nexcom blade servers
running FreeBSD/amd64. The interfaces (two Marvell Yukon 88E8062 controllers)
are recognized properly, but no media is ever detected:
|
Hi,
Pyun YongHyeon wrote:
The 88E8062 support wasn't tested due to lack of hardware and I just
copied the device id from myk driver. Would you show me the output
of "devinfo -rv| grep oui" ? Also it would be better if I can see
verbosed boot message.
Here you go:
# devinfo -rv | grep oui
On Mon, Jun 30, 2008 at 01:54:23PM +0200, Krzysztof Jedruczyk wrote:
> Hi,
>
> I am trying to bring up gigabit interface in couple of Nexcom blade servers
> running FreeBSD/amd64. The interfaces (two Marvell Yukon 88E8062
> controllers) are recognized properly, but no media is ever detected
Hi,
I am trying to bring up gigabit interface in couple of Nexcom blade servers
running FreeBSD/amd64. The interfaces (two Marvell Yukon 88E8062 controllers)
are recognized properly, but no media is ever detected:
> ifconfig
msk0: flags=8802 metric 0 mtu 1500
options=11a
ether 0
12 matches
Mail list logo
