LIST OF OUR SERVICES:
Dear Sir/Madam,
Our company "Construction Management Consultant" is organizing the following
Project Management seminars in KSA
Upcoming Seminars in Jeddah-KSA
Description Start Date End Date
FIDIC Conditions of Contract & Claims Management 8/5/201010/5/2010
Professiona
On Tue, 20 Apr 2010 17:58:17 +0100, Luis Henriques wrote:
>On Tue, Apr 20, 2010 at 12:14:51PM -0400, Adam M. Dutko wrote:
>> Lines identifying the card:
>>
>> ath0 at pci2 dev 0 function 0 "Atheros AR5424" rev 0x01: apic 2 int 17 (irq
>> 10)
>> ath0: AR5424 14.2 phy 7.0 rf 0.0, WOR0W, address XX:
A diff for the ep(4) 3Com EtherLink III driver to clean up the ioctl handler
code a bit and eliminate unnecessary resets when reconfiguring IP addresses.
Please test and provide a dmesg.
Index: elink3.c
===
RCS file: /cvs/src/sys/de
A diff for the ne(4) NE2000 driver to clean up the ioctl handler code
a bit and eliminate unnecessary resets when reconfiguring IP addresses.
Please test and provide a dmesg.
Index: dp8390.c
===
RCS file: /cvs/src/sys/dev/ic/dp8390.
Ce message contient des images, si elles ne s'affichent pas correctement,
cliquez ici,
Unsuscribe, here.
Devis-Avis.com
Energies renouvelables : ` quel prix ?
Economisez jusquâ` 45% en cridit dâimptt
Riduisez votre facture de 50%
Empruntez ` taux 0% (eco-prjt)
Aides et subventions rigionales
PP>P1QQ P9 P4P5P=Q !
P#QP0Q P8P5QQ PP#PP P P3. P P>QP:P2Q - P=P0P8P;QQQP8P5
QP0P1P>QP=P8P:P8 P4P;Q QP0P7P>P2Q Q, P2QP5PQ:
P P0P1P>QP=P8P:P8 QQQP4P5P=QQ b P=P5P4P>QP>P3P> P2Q P?P>P;P=QQ
QQP6P5P;Q P5 P8 P=QP4P=Q P5 P?P5QP5P5P7P4Q ,
QP0P7P3QQP7P:P8, QP>QQP8QP>P2P:P8, P
this is a known unsupported chip. I believe the ISC atheros driver is
compatible, so you may be able to borrow code from linux/freebsd/netbsd
to fix it.
(think of it as a TODO item ;) )
On 2010 Apr 20 (Tue) at 10:55:18 -0400 (-0400), Adam M. Dutko wrote:
:When I attempt to use my wireless card
**
*
* P P PPP"PP'PP!PPP P PP"P PP+ PP.PPPP"PP P PPP PP/ P
P#P P PPPPP P'PP!PP PP P#P'PP"P.
*
**
P P0 QP5PP2P>P4P8QP5P;P8
P:P>PP2Q P5 P
as pointed out by Peter Philipp, there are some problems with
pclose() in sendbug, this code from hwdump() which I borrowed for
usbdevs()..
1 if ((ifp = popen(cmd, "r")) != NULL) {
2 while (!feof(ifp)) {
3 len = fread(buf, 1, sizeof
On 2010/04/20 15:31, Miod Vallat wrote:
> > I think this makes dmesg uglier. The information is easily available
> > from usbdevs(8).
>
> This argues for sendbug(1) adding the output of `usbdevs -v'.
That makes sense to me. Tested on simh-vax and amd64.
Index: sendbug.1
On Tue, Apr 20, 2010 at 12:14:51PM -0400, Adam M. Dutko wrote:
> Lines identifying the card:
>
> ath0 at pci2 dev 0 function 0 "Atheros AR5424" rev 0x01: apic 2 int 17 (irq
> 10)
> ath0: AR5424 14.2 phy 7.0 rf 0.0, WOR0W, address XX:XX:XX:XX:XX:XX
>
> I have the version the other folks had that h
Lines identifying the card:
ath0 at pci2 dev 0 function 0 "Atheros AR5424" rev 0x01: apic 2 int 17 (irq
10)
ath0: AR5424 14.2 phy 7.0 rf 0.0, WOR0W, address XX:XX:XX:XX:XX:XX
I have the version the other folks had that had issues with your patch. I
can still attempt to use the patch if you'd lik
I agree to kettenis's opinion.
Almost all users will not care the VID/PID information even though it is
contained in dmesg. You (and potential bug report user) can get this
information
(with more detail) by usbdevs. isn't it enough?
-- Yojiro UO
On 2010/04/20, at 23:14, Stuart Henderson wrote:
On Tue, Apr 20, 2010 at 4:06 PM, Adam M. Dutko wrote:
> I have a card to test with and am trying to solve the problem on my eeepc
> laptop. Luis, are you still around and interested in working on this?
Yep, still around. But not sure how I can help without the actual HW.
Sometime ago I submited
> I think this makes dmesg uglier. The information is easily available
> from usbdevs(8).
This argues for sendbug(1) adding the output of `usbdevs -v'.
Miod
On Tue, Apr 20, 2010 at 10:55:18AM -0400, Adam M. Dutko wrote:
> When I attempt to use my wireless card (AR5424) I get the following:
>
> ath0: unable to reset hardware; hal status 3520208968
>
> The number at the end changes when I try again.
That smells like an uninitialized value for status,
I have a card to test with and am trying to solve the problem on my eeepc
laptop. Luis, are you still around and interested in working on this?
When I attempt to use my wireless card (AR5424) I get the following:
ath0: unable to reset hardware; hal status 3520208968
The number at the end changes when I try again.
I believe I've traced where the error message is thrown to a section of code
in src/sys/dev/ic/ath.c:
if (!ath_hal_reset(ah
On 2010/04/20 15:46, Mark Kettenis wrote:
> > Date: Tue, 20 Apr 2010 14:23:46 +0100
> > From: Stuart Henderson
> >
> > after reading the N hundredth misc@ post with some USB device
> > where device/vendor IDs haven't been shown, it seems that printing
> > them in the device attach line might save
I like this, but i was also too stupid to run usbdevs to find
vendor/product id for my device (and i'm too embarrassed to tell how
actually found it).
/jtm
On Tue, April 20, 2010 15:23, Stuart Henderson wrote:
> after reading the N hundredth misc@ post with some USB device
> where device/vendor I
> Surely people can move on from the low hanging fruit of a port that needs
> a ./configure & make install, to minor code or makefile changes, to specific
> new functionality to from the scratch coding.
Not to sound like a dick, but this illustrates some of what I'm saying:
If I hold up o
> Date: Tue, 20 Apr 2010 14:23:46 +0100
> From: Stuart Henderson
>
> after reading the N hundredth misc@ post with some USB device
> where device/vendor IDs haven't been shown, it seems that printing
> them in the device attach line might save some trouble.
>
> any comments/suggestions?
I think
On 2010/04/20 14:23, Stuart Henderson wrote:
> after reading the N hundredth misc@ post with some USB device
> where device/vendor IDs haven't been shown, it seems that printing
> them in the device attach line might save some trouble.
>
> any comments/suggestions?
note that with PCI, we print ca
after reading the N hundredth misc@ post with some USB device
where device/vendor IDs haven't been shown, it seems that printing
them in the device attach line might save some trouble.
any comments/suggestions?
Index: usb_subr.c
===
From: "Bret S. Lambert"
Or, in short, we need to not deter people straight away, and accept that
perhaps sometimes decent programmers start from ones that make lots
of mistakes.
Perhaps a ports TODO similar to the NetBSD ports TODO might help; it
doesn't require quite the same level of kernel o
> Or, in short, we need to not deter people straight away, and accept that
> perhaps sometimes decent programmers start from ones that make lots
> of mistakes.
>
> Perhaps a ports TODO similar to the NetBSD ports TODO might help; it
> doesn't require quite the same level of kernel or userspace hac
On Mon, Apr 19, 2010 at 04:15:02PM +, Thordur Bjornsson wrote:
> > And if you value your sanity, stay out of anything resembling filesystems.
> This is a lie.
>
> Hacking on filesystems, and the VFS layer in general is a very rewarding
> experince, just ask Bob.
>
> NFS for example, has been
27 matches
Mail list logo
