Date: Tue, 08 Jul 2008 11:47:51 +0200 From: =?UTF-8?B?S3J6eXN6dG9mIErEmWRydWN6eWs=?= <beaker@hot.pl> To: pyunyh@gmail.com Cc: freebsd-stable@freebsd.org Subject: Re: Marvell Yukon 88E8062 - media selection problem Message-ID: <487337C7.7030705@hot.pl> In-Reply-To: <20080708062443.GE12415@cdnetworks.co.kr> References: <20080701004855.GF83626@cdnetworks.co.kr> <486A07A4.1070406@hot.pl> <20080702010929.GA87933@cdnetworks.co.kr> <486C0E69.8020603@hot.pl> <20080703015948.GB92015@cdnetworks.co.kr> <486CBA1D.6000602@hot.pl> <20080705011612.GC671@cdnetworks.co.kr> <48712EE8.1000701@hot.pl> <20080707102433.GE8171@cdnetworks.co.kr> <487263EF.6070003@hot.pl> <20080708062443.GE12415@cdnetworks.co.kr>
next in thread | previous in thread | raw e-mail | index | archive | help
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 under certain conditions. Orignally msk.88E8040.patch5 > was generated for 88E8040 fast ethernet controller but it miserably > failed to support the controller so I had to think harder to make > it work. :-( > > Anyway I'll commit the minimal patch in a couple of days as it > seems that it wouldn't affect other Yukon II controllers. Ok. I'm not sure I've been clear though: with the smaller patch only one interface worked (but it was msk1 for whatever reason this time). So my question would be: once this patch gets in the tree, would it possible to for me to apply some parts of msk.88E8040.patch5 parts to get both interfaces running? I need to put the only two msk-boxes I currently have in kind of production stage. Currently for testing, but it will be harder for me to test fixes. As of today, I'll set them up with 7-STABLE + msk.88E040.patch5 since this setup was only one that seemed fully functional. Testing will still be possible, since I could schedule some maintenance work on one of the boxes during evenings (luckily only one of affected machines will have to run 24/7). In my current testing I just rebuilt kernel/rebooted with every test which is a bit annoying. I'm certain it would be possible to build affected parts as modules and rebuild->kldunload->kldload only those. Am I right? If it is indeed possible I'd appreciate some instructions on how to do that properly. -- Best regards, Krzysztof Jędruczyk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?487337C7.7030705>