From moonlightakkiy at yahoo.ca  Sun Nov  8 10:22:52 2009
From: moonlightakkiy at yahoo.ca (PseudoCylon)
Date: Sun Nov  8 10:23:05 2009
Subject: finished run driver for CURRENT
Message-ID: <668402.59630.qm@web51804.mail.re2.yahoo.com>

Hello everyone,

I finished porting run driver to CURRENT (sort of). I posted it at freebsd fourums
http://forums.freebsd.org/showpost.php?s=a3756a43cb6eca54dea97673ac8424e7&p=47936&postcount=28
Anyone interested in please try it out.


      __________________________________________________________________
Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail.  Click on Options in Mail and switch to New Mail today or register for free at http://mail.yahoo.ca
From hselasky at c2i.net  Sun Nov  8 13:18:45 2009
From: hselasky at c2i.net (Hans Petter Selasky)
Date: Sun Nov  8 13:18:51 2009
Subject: finished run driver for CURRENT
In-Reply-To: <668402.59630.qm@web51804.mail.re2.yahoo.com>
References: <668402.59630.qm@web51804.mail.re2.yahoo.com>
Message-ID: <200911081320.04408.hselasky@c2i.net>

On Sunday 08 November 2009 11:22:50 PseudoCylon wrote:
> Hello everyone,
>
> I finished porting run driver to CURRENT (sort of). I posted it at freebsd
> fourums
> http://forums.freebsd.org/showpost.php?s=a3756a43cb6eca54dea97673ac8424e7&p
>=47936&postcount=28 Anyone interested in please try it out.

Just some comments:

There is an ep_index field you can set, instead of specifying exactly which 
endpoint to use.

Eg.

UE_BULK_IN
UE_ADDR_ANY

ep_index = 0, /* will match first bulk_in + addr_any */


UE_BULK_OUT
UE_ADDR_ANY

ep_index = 2, /* will match third bulk_out + addr_any */

I'm not sure if the manufacturer will change those values?

Else, do you have any other feedback on the new USB stack? Was it difficult?

--HPS

From ganbold at micom.mng.net  Sun Nov  8 15:50:27 2009
From: ganbold at micom.mng.net (Ganbold)
Date: Sun Nov  8 15:50:50 2009
Subject: finished run driver for CURRENT
In-Reply-To: <668402.59630.qm@web51804.mail.re2.yahoo.com>
References: <668402.59630.qm@web51804.mail.re2.yahoo.com>
Message-ID: <4AF6DFA9.8080303@micom.mng.net>

PseudoCylon wrote:
> Hello everyone,
>
> I finished porting run driver to CURRENT (sort of). I posted it at freebsd fourums
> http://forums.freebsd.org/showpost.php?s=a3756a43cb6eca54dea97673ac8424e7&p=47936&postcount=28
> Anyone interested in please try it out.
>   

Compile fails at line 2338 of if_run.c.

/home/tsgan/run-CUR/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:
In function 'run_tx':
/home/tsgan/run-CUR/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:2338:
warning: comparison between pointer and integer
*** Error code 1

Stop in /home/tsgan/run-CUR/sys/modules/usb/run.

I guess it should either:

        struct ieee80211_channel *chan;
        chan = ni->ni_chan == IEEE80211_CHAN_ANYC ? ic->ic_curchan :
ni->ni_chan;

or:

        struct ieee80211_channel *chan;
        chan = ni->ni_chan == (ieee80211_channel *)IEEE80211_CHAN_ANY ?
ic->ic_curchan : ni->ni_chan;

I didn't test association with AP (don't have AP), system finds usb
wireless Planex GW-USMicroN device:

Nov  8 23:08:00 beastie kernel: ugen3.3: <Ralink> at usbus3
Nov  8 23:08:00 beastie kernel: run0: <1.0> on usbus3
Nov  8 23:08:00 beastie kernel: run0: MAC/BBP RT3070 (rev 0x0200), RF
RT3020 (MIMO 1T1R), address 00:22:cf:03:e0:30
Nov  8 23:08:00 beastie kernel: run0: You are using firmware RT2870.


run0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 2290
        ether 00:22:cf:03:e0:30
        media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
        status: no carrier


regards,

Ganbold Ts.

>
>       __________________________________________________________________
> Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail.  Click on Options in Mail and switch to New Mail today or register for free at http://mail.yahoo.ca
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>
>
>
>   


-- 
He who laughs last hasn't been told the terrible truth.
From moonlightakkiy at yahoo.ca  Mon Nov  9 05:44:53 2009
From: moonlightakkiy at yahoo.ca (PseudoCylon)
Date: Mon Nov  9 05:44:59 2009
Subject: finished run driver for CURRENT
In-Reply-To: <668402.59630.qm@web51804.mail.re2.yahoo.com>
References: <668402.59630.qm@web51804.mail.re2.yahoo.com>
Message-ID: <366719.85562.qm@web51805.mail.re2.yahoo.com>

----- Original Message ----
> Subject: Re: finished run driver for CURRENT
> 
> On Sunday 08 November 2009 11:22:50 PseudoCylon wrote:
> > Hello everyone,
> >
> > I finished porting run driver to CURRENT (sort of). I posted it at freebsd
> > fourums
> > http://forums.freebsd.org/showpost.php?s=a3756a43cb6eca54dea97673ac8424e7&p
> >=47936&postcount=28 Anyone interested in please try it out.
> 
> Just some comments:
> 
> There is an ep_index field you can set, instead of specifying exactly which 
> endpoint to use.
> 
> Eg.
> 
> UE_BULK_IN
> UE_ADDR_ANY
> 
> ep_index = 0, /* will match first bulk_in + addr_any */
> 
> 
> UE_BULK_OUT
> UE_ADDR_ANY
> 
> ep_index = 2, /* will match third bulk_out + addr_any */
> 
> I'm not sure if the manufacturer will change those values?
> 
> Else, do you have any other feedback on the new USB stack? Was it difficult?
> 
> --HPS

> 
> Compile fails at line 2338 of if_run.c.
> 
> /home/tsgan/run-CUR/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:
> In function 'run_tx':
> /home/tsgan/run-CUR/sys/modules/usb/run/../../../dev/usb/wlan/if_run.c:2338:
> warning: comparison between pointer and integer
> *** Error code 1
> 
> Stop in /home/tsgan/run-CUR/sys/modules/usb/run.
> 
> I guess it should either:
> 
>         struct ieee80211_channel *chan;
>         chan = ni->ni_chan == IEEE80211_CHAN_ANYC ? ic->ic_curchan :
> ni->ni_chan;
> 
> or:
> 
>         struct ieee80211_channel *chan;
>         chan = ni->ni_chan == (ieee80211_channel *)IEEE80211_CHAN_ANY ?
> ic->ic_curchan : ni->ni_chan;
> 

Thank you to everyone testing the driver. I've implemented all suggestions.


      __________________________________________________________________
Get a sneak peak at messages with a handy reading pane with All new Yahoo! Mail: http://ca.promos.yahoo.com/newmail/overview2/
From brendan.kennedy at gmail.com  Wed Nov 11 15:18:17 2009
From: brendan.kennedy at gmail.com (Brendan Kennedy)
Date: Wed Nov 11 15:18:25 2009
Subject: Driver code release
Message-ID: <db3b765b0911110647j7570a86fnc06074e055b87f59@mail.gmail.com>

Hi All,

I have some driver code that is utilised through opencrypto for my
hardware. I?d like to have this code integrated into FreeBSD similarly
to the hifn driver.
Could you give me some pointers as to how this should be done?

Can such code still be included in the FreeBSD 7 code base?

I also have an opencrypto patch for your consideration. Is this the
correct group to mail such a patch to?

Best Regards,
Brendan
From janis at grotus.lv  Thu Nov 12 10:43:14 2009
From: janis at grotus.lv (=?UTF-8?Q?J=C4=81nis_Grotus?=)
Date: Thu Nov 12 10:43:21 2009
Subject: Support for VT2020
Message-ID: <70039a55ff1fa8a0323054e7e7f0710e@pop3.sigmanet.lv>

Hello!

Is anybody working on driver for VT2020 sound chip? Maybe I can help
somehow to get it working?

BR
J?nis
From jhb at freebsd.org  Thu Nov 12 15:32:05 2009
From: jhb at freebsd.org (John Baldwin)
Date: Thu Nov 12 15:32:16 2009
Subject: Driver code release
In-Reply-To: <db3b765b0911110647j7570a86fnc06074e055b87f59@mail.gmail.com>
References: <db3b765b0911110647j7570a86fnc06074e055b87f59@mail.gmail.com>
Message-ID: <200911121024.18601.jhb@freebsd.org>

On Wednesday 11 November 2009 9:47:06 am Brendan Kennedy wrote:
> Hi All,
> 
> I have some driver code that is utilised through opencrypto for my
> hardware. I?d like to have this code integrated into FreeBSD similarly
> to the hifn driver.
> Could you give me some pointers as to how this should be done?
> 
> Can such code still be included in the FreeBSD 7 code base?
> 
> I also have an opencrypto patch for your consideration. Is this the
> correct group to mail such a patch to?

I'm not very familiar with opencrypto myself, but Philip (cc'd) is and might 
be able to point you in the right direction.

-- 
John Baldwin
From jhb at freebsd.org  Thu Nov 12 15:32:06 2009
From: jhb at freebsd.org (John Baldwin)
Date: Thu Nov 12 15:32:16 2009
Subject: Support for VT2020
In-Reply-To: <70039a55ff1fa8a0323054e7e7f0710e@pop3.sigmanet.lv>
References: <70039a55ff1fa8a0323054e7e7f0710e@pop3.sigmanet.lv>
Message-ID: <200911121026.08767.jhb@freebsd.org>

On Thursday 12 November 2009 5:24:37 am J?nis Grotus wrote:
> Hello!
> 
> Is anybody working on driver for VT2020 sound chip? Maybe I can help
> somehow to get it working?

Perhaps try asking on the freebsd-multimedia@ list?  I think that is where the 
folks who maintain the audio drivers hang out.  This list is largely for 
asking questions about device driver development.

-- 
John Baldwin
From philip at freebsd.org  Thu Nov 12 15:36:03 2009
From: philip at freebsd.org (Philip Paeps)
Date: Thu Nov 12 15:36:08 2009
Subject: Driver code release
In-Reply-To: <200911121024.18601.jhb@freebsd.org>
References: <db3b765b0911110647j7570a86fnc06074e055b87f59@mail.gmail.com>
	<200911121024.18601.jhb@freebsd.org>
Message-ID: <20091112153559.GM8230@rincewind.paeps.cx>

On 2009-11-12 10:24:18 (-0500), John Baldwin <jhb@freebsd.org> wrote:
> On Wednesday 11 November 2009 9:47:06 am Brendan Kennedy wrote:
> > Hi All,
> > 
> > I have some driver code that is utilised through opencrypto for my
> > hardware. I?d like to have this code integrated into FreeBSD similarly
> > to the hifn driver.
> > Could you give me some pointers as to how this should be done?
> > 
> > Can such code still be included in the FreeBSD 7 code base?
> > 
> > I also have an opencrypto patch for your consideration. Is this the
> > correct group to mail such a patch to?
> 
> I'm not very familiar with opencrypto myself, but Philip (cc'd) is and might 
> be able to point you in the right direction.

Hi Brendan!  I would indeed be very happy to look at your patch and commit it.
I would like to keep opencrypto in 7.x in sync with head (and 8.x) at least
for the forseeable future, so I don't think merging to 7.x will be a problem.

Provided the code works, of course. ;-)

Feel free to send me the code and I'll take a look.

Thanks!

 - Philip

-- 
Philip Paeps                                  Made from non-edible parts
philip@freebsd.org
From mav at FreeBSD.org  Thu Nov 12 19:26:13 2009
From: mav at FreeBSD.org (Alexander Motin)
Date: Thu Nov 12 19:26:19 2009
Subject: Support for VT2020
In-Reply-To: <1258035782.00182823.1258023001@10.7.7.3>
References: <1258035782.00182823.1258023001@10.7.7.3>
Message-ID: <4AFC5B44.4050204@FreeBSD.org>

J?nis Grotus wrote:
> Is anybody working on driver for VT2020 sound chip? Maybe I can help
> somehow to get it working?

Quick Googling tells me that it is HDA codec. Have you tried snd_hda
driver? It is quite flexible to support even unknown codecs.

Load snd_hda module via loader.conf, boot kernel with verbose messages
and send me complete dmesg output for investigation please.

-- 
Alexander Motin
From patfbsd at davenulle.org  Thu Nov 12 19:59:06 2009
From: patfbsd at davenulle.org (Patrick Lamaiziere)
Date: Thu Nov 12 19:59:13 2009
Subject: Driver code release
In-Reply-To: <db3b765b0911110647j7570a86fnc06074e055b87f59@mail.gmail.com>
References: <db3b765b0911110647j7570a86fnc06074e055b87f59@mail.gmail.com>
Message-ID: <20091112204205.4d8c0c5b@baby-jane.lamaiziere.net>

Le Wed, 11 Nov 2009 14:47:06 +0000,
Brendan Kennedy <brendan.kennedy@gmail.com> a ?crit :

> Hi All,

Hello,

> I have some driver code that is utilised through opencrypto for my
> hardware. I?d like to have this code integrated into FreeBSD similarly
> to the hifn driver.
> Could you give me some pointers as to how this should be done?
> 
> Can such code still be included in the FreeBSD 7 code base?
> 
> I also have an opencrypto patch for your consideration. Is this the
> correct group to mail such a patch to?

I would be happy to read the code (just to see), could you provide a
link to the code?

Thanks, regards.
From janis at grotus.lv  Thu Nov 12 20:43:05 2009
From: janis at grotus.lv (=?iso-8859-13?B?SuJuaXM=?=)
Date: Thu Nov 12 20:43:12 2009
Subject: Support for VT2020
In-Reply-To: <4AFC5B44.4050204@FreeBSD.org>
References: <1258035782.00182823.1258023001@10.7.7.3>
	<4AFC5B44.4050204@FreeBSD.org>
Message-ID: <op.u3auh9jullsx4c@zhux.lan>

Here is little more info what I have done:

http://forums.freebsd.org/showthread.php?t=8253

I'll provide You with dmesg output little later.

BR
Janis

On Thu, 12 Nov 2009 21:00:20 +0200, Alexander Motin <mav@freebsd.org>  
wrote:

> J?nis Grotus wrote:
>> Is anybody working on driver for VT2020 sound chip? Maybe I can help
>> somehow to get it working?
>
> Quick Googling tells me that it is HDA codec. Have you tried snd_hda
> driver? It is quite flexible to support even unknown codecs.
>
> Load snd_hda module via loader.conf, boot kernel with verbose messages
> and send me complete dmesg output for investigation please.
>


-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
From mav at FreeBSD.org  Thu Nov 12 21:16:00 2009
From: mav at FreeBSD.org (Alexander Motin)
Date: Thu Nov 12 21:16:06 2009
Subject: Support for VT2020
In-Reply-To: <op.u3auh9jullsx4c@zhux.lan>
References: <1258035782.00182823.1258023001@10.7.7.3>
	<4AFC5B44.4050204@FreeBSD.org> <op.u3auh9jullsx4c@zhux.lan>
Message-ID: <4AFC7B0C.1030504@FreeBSD.org>

J?nis wrote:
> Here is little more info what I have done:
> 
> http://forums.freebsd.org/showthread.php?t=8253
> 
> I'll provide You with dmesg output little later.

HDMI audio part may also depend on video driver to work. It is mostly
untested area.
VIA codec same time has better chances to work, but it is first time I
have heard about this model, more info and testing needed.

-- 
Alexander Motin
From janis at grotus.lv  Thu Nov 12 22:30:06 2009
From: janis at grotus.lv (=?iso-8859-13?B?SuJuaXM=?=)
Date: Thu Nov 12 22:30:17 2009
Subject: Support for VT2020
In-Reply-To: <4AFC7B0C.1030504@FreeBSD.org>
References: <1258035782.00182823.1258023001@10.7.7.3>
	<4AFC5B44.4050204@FreeBSD.org> <op.u3auh9jullsx4c@zhux.lan>
	<4AFC7B0C.1030504@FreeBSD.org>
Message-ID: <op.u3azgi1vllsx4c@zhux.lan>

My dmesg.boot file in attachment...

Janis

On Thu, 12 Nov 2009 23:15:56 +0200, Alexander Motin <mav@freebsd.org>  
wrote:

> J?nis wrote:
>> Here is little more info what I have done:
>>
>> http://forums.freebsd.org/showthread.php?t=8253
>>
>> I'll provide You with dmesg output little later.
>
> HDMI audio part may also depend on video driver to work. It is mostly
> untested area.
> VIA codec same time has better chances to work, but it is first time I
> have heard about this model, more info and testing needed.
>


-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dmesg.boot
Type: application/octet-stream
Size: 63806 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-drivers/attachments/20091112/ba623e78/dmesg.obj
From mav at FreeBSD.org  Thu Nov 12 22:58:26 2009
From: mav at FreeBSD.org (Alexander Motin)
Date: Thu Nov 12 22:58:33 2009
Subject: Support for VT2020
In-Reply-To: <op.u3azgi1vllsx4c@zhux.lan>
References: <1258035782.00182823.1258023001@10.7.7.3>
	<4AFC5B44.4050204@FreeBSD.org> <op.u3auh9jullsx4c@zhux.lan>
	<4AFC7B0C.1030504@FreeBSD.org> <op.u3azgi1vllsx4c@zhux.lan>
Message-ID: <4AFC930E.9070408@FreeBSD.org>

J?nis wrote:
> My dmesg.boot file in attachment...

Looks fine. I don't see any problem. Have you tested it?
I'll recheck codec IDs list tomorrow to add this one.

-- 
Alexander Motin
From janis at grotus.lv  Fri Nov 13 07:19:39 2009
From: janis at grotus.lv (=?UTF-8?Q?J=C4=81nis_Grotus?=)
Date: Fri Nov 13 07:19:46 2009
Subject: Support for VT2020
In-Reply-To: <4AFC930E.9070408@FreeBSD.org>
References: <1258035782.00182823.1258023001@10.7.7.3>
	<4AFC5B44.4050204@FreeBSD.org> <op.u3auh9jullsx4c@zhux.lan>
	<4AFC7B0C.1030504@FreeBSD.org> <op.u3azgi1vllsx4c@zhux.lan>
	<4AFC930E.9070408@FreeBSD.org>
Message-ID: <49901f313e6c7a160646c1489197decb@pop3.sigmanet.lv>

I tried to play some video with VLC, played with audio options. Tried to
play mp3 and tried 
cat filename > /dev/dsp
what was suggested in handbook. Also plugged in headphones to test other
outputs than hdmi.

How else can I test it?

Janis

On Fri, 13 Nov 2009 00:58:22 +0200, Alexander Motin <mav@FreeBSD.org>
wrote:
> J?nis wrote:
>> My dmesg.boot file in attachment...
> 
> Looks fine. I don't see any problem. Have you tested it?
> I'll recheck codec IDs list tomorrow to add this one.
From mav at FreeBSD.org  Fri Nov 13 08:43:07 2009
From: mav at FreeBSD.org (Alexander Motin)
Date: Fri Nov 13 08:43:15 2009
Subject: Support for VT2020
In-Reply-To: <49901f313e6c7a160646c1489197decb@pop3.sigmanet.lv>
References: <1258035782.00182823.1258023001@10.7.7.3>
	<4AFC5B44.4050204@FreeBSD.org> <op.u3auh9jullsx4c@zhux.lan>
	<4AFC7B0C.1030504@FreeBSD.org> <op.u3azgi1vllsx4c@zhux.lan>
	<4AFC930E.9070408@FreeBSD.org>
	<49901f313e6c7a160646c1489197decb@pop3.sigmanet.lv>
Message-ID: <4AFD1C17.4040908@FreeBSD.org>

J?nis Grotus wrote:
> I tried to play some video with VLC, played with audio options. Tried to
> play mp3 and tried 
> cat filename > /dev/dsp
> what was suggested in handbook. Also plugged in headphones to test other
> outputs than hdmi.
> 
> How else can I test it?

By default all sound goes to the first device (in your case HDMI port).
HDMI may not work for reasons not depending from snd_hda driver.
To use other outputs you may use other dspX or set hw.snd.default_unit
sysctl. It is very often problem. Read snd_hda(4) man page carefully.

-- 
Alexander Motin
From janis at grotus.lv  Fri Nov 13 09:20:01 2009
From: janis at grotus.lv (=?UTF-8?Q?J=C4=81nis_Grotus?=)
Date: Fri Nov 13 09:20:08 2009
Subject: Support for VT2020
In-Reply-To: <4AFD1C17.4040908@FreeBSD.org>
References: <1258035782.00182823.1258023001@10.7.7.3>
	<4AFC5B44.4050204@FreeBSD.org> <op.u3auh9jullsx4c@zhux.lan>
	<4AFC7B0C.1030504@FreeBSD.org> <op.u3azgi1vllsx4c@zhux.lan>
	<4AFC930E.9070408@FreeBSD.org>
	<49901f313e6c7a160646c1489197decb@pop3.sigmanet.lv>
	<4AFD1C17.4040908@FreeBSD.org>
Message-ID: <33b858bb2f72f1c91c559c8f6f98e26b@pop3.sigmanet.lv>

As I undersand from snd_hda man page:
Only audio functions are supported by snd_hda.  Modem, HDMI and other
possible functions are not implemented.

HDMI shoul'd not work.

So I'll try what You suggested when I get home.

Thank's for Your help!
Janis 


> By default all sound goes to the first device (in your case HDMI port).
> HDMI may not work for reasons not depending from snd_hda driver.
> To use other outputs you may use other dspX or set hw.snd.default_unit
> sysctl. It is very often problem. Read snd_hda(4) man page carefully.
From mav at FreeBSD.org  Fri Nov 13 09:25:55 2009
From: mav at FreeBSD.org (Alexander Motin)
Date: Fri Nov 13 09:26:01 2009
Subject: Support for VT2020
In-Reply-To: <33b858bb2f72f1c91c559c8f6f98e26b@pop3.sigmanet.lv>
References: <1258035782.00182823.1258023001@10.7.7.3>
	<4AFC5B44.4050204@FreeBSD.org> <op.u3auh9jullsx4c@zhux.lan>
	<4AFC7B0C.1030504@FreeBSD.org> <op.u3azgi1vllsx4c@zhux.lan>
	<4AFC930E.9070408@FreeBSD.org>
	<49901f313e6c7a160646c1489197decb@pop3.sigmanet.lv>
	<4AFD1C17.4040908@FreeBSD.org>
	<33b858bb2f72f1c91c559c8f6f98e26b@pop3.sigmanet.lv>
Message-ID: <4AFD261E.4010807@FreeBSD.org>

J?nis Grotus wrote:
> As I undersand from snd_hda man page:
> Only audio functions are supported by snd_hda.  Modem, HDMI and other
> possible functions are not implemented.
> 
> HDMI shoul'd not work.

Original HDA specification declares HDMI as something different (not
audio device, but something unknown). But existing HDMI codecs report
them self as Audio codecs. So it is not about this case.

-- 
Alexander Motin
From brendan.kennedy at gmail.com  Fri Nov 13 15:20:19 2009
From: brendan.kennedy at gmail.com (Brendan Kennedy)
Date: Fri Nov 13 15:20:25 2009
Subject: Driver code release
In-Reply-To: <20091112153559.GM8230@rincewind.paeps.cx>
References: <db3b765b0911110647j7570a86fnc06074e055b87f59@mail.gmail.com>
	<200911121024.18601.jhb@freebsd.org>
	<20091112153559.GM8230@rincewind.paeps.cx>
Message-ID: <db3b765b0911130720l2f750669mb89c9f526f949103@mail.gmail.com>

Hi Philip, John,

Thanks for your responses! Unfortunately I've run into a bit of a
delay with releasing this code. I should be able to make it available
sometime over the next forthnight.

Best Regards,
Brendan

2009/11/12 Philip Paeps <philip@freebsd.org>:
> On 2009-11-12 10:24:18 (-0500), John Baldwin <jhb@freebsd.org> wrote:
>> On Wednesday 11 November 2009 9:47:06 am Brendan Kennedy wrote:
>> > Hi All,
>> >
>> > I have some driver code that is utilised through opencrypto for my
>> > hardware. I?d like to have this code integrated into FreeBSD similarly
>> > to the hifn driver.
>> > Could you give me some pointers as to how this should be done?
>> >
>> > Can such code still be included in the FreeBSD 7 code base?
>> >
>> > I also have an opencrypto patch for your consideration. Is this the
>> > correct group to mail such a patch to?
>>
>> I'm not very familiar with opencrypto myself, but Philip (cc'd) is and might
>> be able to point you in the right direction.
>
> Hi Brendan! ?I would indeed be very happy to look at your patch and commit it.
> I would like to keep opencrypto in 7.x in sync with head (and 8.x) at least
> for the forseeable future, so I don't think merging to 7.x will be a problem.
>
> Provided the code works, of course. ;-)
>
> Feel free to send me the code and I'll take a look.
>
> Thanks!
>
> ?- Philip
>
> --
> Philip Paeps ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?Made from non-edible parts
> philip@freebsd.org
>
From janis at grotus.lv  Tue Nov 17 22:13:58 2009
From: janis at grotus.lv (=?iso-8859-13?B?SuJuaXM=?=)
Date: Tue Nov 17 22:14:05 2009
Subject: Support for VT2020
In-Reply-To: <4AFD261E.4010807@FreeBSD.org>
References: <1258035782.00182823.1258023001@10.7.7.3>
	<4AFC5B44.4050204@FreeBSD.org> <op.u3auh9jullsx4c@zhux.lan>
	<4AFC7B0C.1030504@FreeBSD.org> <op.u3azgi1vllsx4c@zhux.lan>
	<4AFC930E.9070408@FreeBSD.org>
	<49901f313e6c7a160646c1489197decb@pop3.sigmanet.lv>
	<4AFD1C17.4040908@FreeBSD.org>
	<33b858bb2f72f1c91c559c8f6f98e26b@pop3.sigmanet.lv>
	<4AFD261E.4010807@FreeBSD.org>
Message-ID: <op.u3j71gopllsx4c@zhux.private>

At last my HTPC have sound :)

That's what I did:
mpg123 -a /dev/dsp0 *.mp3
mpg123 -a /dev/dsp1 *.mp3
mpg123 -a /dev/dsp2 *.mp3
mpg123 -a /dev/dsp3 *.mp3

But only on dsp1 I got sound. So I have sound only at rear (like  
headphone)outputs. Sound on HDMI is not working and front panel jacks have  
no output too. Have not tested RCA and optical S/PDIF yet.

Changing output in gnome's sound preferences did not give any result thats  
why I thought at the beginning that this chip is not supported.
But changing hw.snd.default_unit to 1(as You suggested) helped.

BR
Janis

On Fri, 13 Nov 2009 11:25:50 +0200, Alexander Motin <mav@freebsd.org>  
wrote:
>
> Original HDA specification declares HDMI as something different (not
> audio device, but something unknown). But existing HDMI codecs report
> them self as Audio codecs. So it is not about this case.
>


-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
From obrien654j at gmail.com  Sun Nov 22 18:18:04 2009
From: obrien654j at gmail.com (Jeremy O'Brien)
Date: Sun Nov 22 18:18:12 2009
Subject: Cisco Aironet MPI350 Fix
Message-ID: <20091122175555.GA15539@minifree.wright.edu>

Hello,

I have a Cisco Aironet MPI350 PCI card in my Thinkpad X31, and on a
fresh install of FreeBSD 8.0-RC3, the card did not work. Also, it caused
my system to freeze up for a few seconds about once a minute as the
driver spit out "an0: device timeout" messages so long as the interface
was up. I researched the issue, and found the following fix already in
dragonflybsd's tree:

http://gitweb.dragonflybsd.org/dragonfly.git/commit/7a2a04db44efafea257db883ae3eb5e4ebf2ece9

I modified the patch and applied it to FreeBSD's kernel (trivial), and
am happy to report that my card is now working flawlessly. Could someone
possibly review this patch and integrate it into the source tree so that
others may benefit from it as well?

The patch is based off of 8.0-RC3's code, but applies to the latest code
as well without modification.

Thank you,
Jeremy O'Brien
From jhb at freebsd.org  Mon Nov 23 15:01:58 2009
From: jhb at freebsd.org (John Baldwin)
Date: Mon Nov 23 15:02:09 2009
Subject: Cisco Aironet MPI350 Fix
In-Reply-To: <20091122175555.GA15539@minifree.wright.edu>
References: <20091122175555.GA15539@minifree.wright.edu>
Message-ID: <200911231001.51082.jhb@freebsd.org>

On Sunday 22 November 2009 12:55:55 pm Jeremy O'Brien wrote:
> Hello,
> 
> I have a Cisco Aironet MPI350 PCI card in my Thinkpad X31, and on a
> fresh install of FreeBSD 8.0-RC3, the card did not work. Also, it caused
> my system to freeze up for a few seconds about once a minute as the
> driver spit out "an0: device timeout" messages so long as the interface
> was up. I researched the issue, and found the following fix already in
> dragonflybsd's tree:
> 
> 
http://gitweb.dragonflybsd.org/dragonfly.git/commit/7a2a04db44efafea257db883ae3eb5e4ebf2ece9
> 
> I modified the patch and applied it to FreeBSD's kernel (trivial), and
> am happy to report that my card is now working flawlessly. Could someone
> possibly review this patch and integrate it into the source tree so that
> others may benefit from it as well?
> 
> The patch is based off of 8.0-RC3's code, but applies to the latest code
> as well without modification.

Can you try this version?  The IFF_DRV_OACTIVE bits don't look correct to me 
so I've left them out.  I also changed the driver to use bus_*() vs 
bus_space_*().

-- 
John Baldwin
From obrien654j at gmail.com  Mon Nov 23 20:25:08 2009
From: obrien654j at gmail.com (Jeremy O'Brien)
Date: Mon Nov 23 20:25:41 2009
Subject: Cisco Aironet MPI350 Fix
In-Reply-To: <200911231001.51082.jhb@freebsd.org>
References: <20091122175555.GA15539@minifree.wright.edu>
	<200911231001.51082.jhb@freebsd.org>
Message-ID: <20091123203008.GA26284@archimedes>

On Mon, Nov 23, 2009 at 10:01:50AM -0500, John Baldwin wrote:
> On Sunday 22 November 2009 12:55:55 pm Jeremy O'Brien wrote:
> > Hello,
> > 
> > I have a Cisco Aironet MPI350 PCI card in my Thinkpad X31, and on a
> > fresh install of FreeBSD 8.0-RC3, the card did not work. Also, it caused
> > my system to freeze up for a few seconds about once a minute as the
> > driver spit out "an0: device timeout" messages so long as the interface
> > was up. I researched the issue, and found the following fix already in
> > dragonflybsd's tree:
> > 
> > 
> http://gitweb.dragonflybsd.org/dragonfly.git/commit/7a2a04db44efafea257db883ae3eb5e4ebf2ece9
> > 
> > I modified the patch and applied it to FreeBSD's kernel (trivial), and
> > am happy to report that my card is now working flawlessly. Could someone
> > possibly review this patch and integrate it into the source tree so that
> > others may benefit from it as well?
> > 
> > The patch is based off of 8.0-RC3's code, but applies to the latest code
> > as well without modification.
> 
> Can you try this version?  The IFF_DRV_OACTIVE bits don't look correct to me 
> so I've left them out.  I also changed the driver to use bus_*() vs 
> bus_space_*().
> 
> -- 
> John Baldwin

In my initial tests, my card is not working. This is on my university 
network, so I will try again on my home network and report back the results. 
As a side note, it takes about thirty minutes for me to rebuild my kernel. 
I'm using make buildkernel everytime. Is there a faster method of 
recompiling?
From obrien654j at gmail.com  Mon Nov 23 21:17:11 2009
From: obrien654j at gmail.com (Jeremy O'Brien)
Date: Mon Nov 23 21:17:17 2009
Subject: Cisco Aironet MPI350 Fix
In-Reply-To: <200911231001.51082.jhb@freebsd.org>
References: <20091122175555.GA15539@minifree.wright.edu>
	<200911231001.51082.jhb@freebsd.org>
Message-ID: <20091123211734.GA1207@minifree>

On Mon, Nov 23, 2009 at 10:01:50AM -0500, John Baldwin wrote:
> On Sunday 22 November 2009 12:55:55 pm Jeremy O'Brien wrote:
> > Hello,
> > 
> > I have a Cisco Aironet MPI350 PCI card in my Thinkpad X31, and on a
> > fresh install of FreeBSD 8.0-RC3, the card did not work. Also, it caused
> > my system to freeze up for a few seconds about once a minute as the
> > driver spit out "an0: device timeout" messages so long as the interface
> > was up. I researched the issue, and found the following fix already in
> > dragonflybsd's tree:
> > 
> > 
> http://gitweb.dragonflybsd.org/dragonfly.git/commit/7a2a04db44efafea257db883ae3eb5e4ebf2ece9
> > 
> > I modified the patch and applied it to FreeBSD's kernel (trivial), and
> > am happy to report that my card is now working flawlessly. Could someone
> > possibly review this patch and integrate it into the source tree so that
> > others may benefit from it as well?
> > 
> > The patch is based off of 8.0-RC3's code, but applies to the latest code
> > as well without modification.
> 
> Can you try this version?  The IFF_DRV_OACTIVE bits don't look correct to me 
> so I've left them out.  I also changed the driver to use bus_*() vs 
> bus_space_*().
> 
> -- 
> John Baldwin

Tried it at home, worked great. My university's wireless is shoddy.
From imp at bsdimp.com  Mon Nov 23 21:49:49 2009
From: imp at bsdimp.com (M. Warner Losh)
Date: Mon Nov 23 21:49:55 2009
Subject: Cisco Aironet MPI350 Fix
In-Reply-To: <20091123203008.GA26284@archimedes>
References: <20091122175555.GA15539@minifree.wright.edu>
	<200911231001.51082.jhb@freebsd.org>
	<20091123203008.GA26284@archimedes>
Message-ID: <20091123.143946.-1431868910.imp@bsdimp.com>

In message: <20091123203008.GA26284@archimedes>
            "Jeremy O'Brien" <obrien654j@gmail.com> writes:
: I'm using make buildkernel everytime. Is there a faster method of 
: recompiling?

make buildkernel KERNCONF=FOO		# first time
make buildkernel KERNFAST=FOO		# after that

Warner
From obrien654j at gmail.com  Tue Nov 24 04:30:03 2009
From: obrien654j at gmail.com (Jeremy O'Brien)
Date: Tue Nov 24 04:30:10 2009
Subject: Cisco Aironet MPI350 Fix
In-Reply-To: <20091123211734.GA1207@minifree>
References: <20091122175555.GA15539@minifree.wright.edu>
	<200911231001.51082.jhb@freebsd.org>
	<20091123211734.GA1207@minifree>
Message-ID: <20091124043015.GA21209@goldengraham>

On Mon, Nov 23, 2009 at 04:17:34PM -0500, Jeremy O'Brien wrote:
> On Mon, Nov 23, 2009 at 10:01:50AM -0500, John Baldwin wrote:
> > On Sunday 22 November 2009 12:55:55 pm Jeremy O'Brien wrote:
> > > Hello,
> > > 
> > > I have a Cisco Aironet MPI350 PCI card in my Thinkpad X31, and on a
> > > fresh install of FreeBSD 8.0-RC3, the card did not work. Also, it caused
> > > my system to freeze up for a few seconds about once a minute as the
> > > driver spit out "an0: device timeout" messages so long as the interface
> > > was up. I researched the issue, and found the following fix already in
> > > dragonflybsd's tree:
> > > 
> > > 
> > http://gitweb.dragonflybsd.org/dragonfly.git/commit/7a2a04db44efafea257db883ae3eb5e4ebf2ece9
> > > 
> > > I modified the patch and applied it to FreeBSD's kernel (trivial), and
> > > am happy to report that my card is now working flawlessly. Could someone
> > > possibly review this patch and integrate it into the source tree so that
> > > others may benefit from it as well?
> > > 
> > > The patch is based off of 8.0-RC3's code, but applies to the latest code
> > > as well without modification.
> > 
> > Can you try this version?  The IFF_DRV_OACTIVE bits don't look correct to me 
> > so I've left them out.  I also changed the driver to use bus_*() vs 
> > bus_space_*().
> > 
> > -- 
> > John Baldwin
> 
> Tried it at home, worked great. My university's wireless is shoddy.

I'm not sure if this is related to your patch or not, but I've been
getting spurts of kernel: stray irq7 messages that I don't recall
getting before the patch. Do you think it could be related?
From jhb at freebsd.org  Tue Nov 24 18:18:26 2009
From: jhb at freebsd.org (John Baldwin)
Date: Tue Nov 24 18:18:52 2009
Subject: Cisco Aironet MPI350 Fix
In-Reply-To: <20091124043015.GA21209@goldengraham>
References: <20091122175555.GA15539@minifree.wright.edu>
	<20091123211734.GA1207@minifree>
	<20091124043015.GA21209@goldengraham>
Message-ID: <200911241305.33470.jhb@freebsd.org>

On Monday 23 November 2009 11:30:15 pm Jeremy O'Brien wrote:
> On Mon, Nov 23, 2009 at 04:17:34PM -0500, Jeremy O'Brien wrote:
> > On Mon, Nov 23, 2009 at 10:01:50AM -0500, John Baldwin wrote:
> > > On Sunday 22 November 2009 12:55:55 pm Jeremy O'Brien wrote:
> > > > Hello,
> > > > 
> > > > I have a Cisco Aironet MPI350 PCI card in my Thinkpad X31, and on a
> > > > fresh install of FreeBSD 8.0-RC3, the card did not work. Also, it caused
> > > > my system to freeze up for a few seconds about once a minute as the
> > > > driver spit out "an0: device timeout" messages so long as the interface
> > > > was up. I researched the issue, and found the following fix already in
> > > > dragonflybsd's tree:
> > > > 
> > > > 
> > > http://gitweb.dragonflybsd.org/dragonfly.git/commit/7a2a04db44efafea257db883ae3eb5e4ebf2ece9
> > > > 
> > > > I modified the patch and applied it to FreeBSD's kernel (trivial), and
> > > > am happy to report that my card is now working flawlessly. Could someone
> > > > possibly review this patch and integrate it into the source tree so that
> > > > others may benefit from it as well?
> > > > 
> > > > The patch is based off of 8.0-RC3's code, but applies to the latest code
> > > > as well without modification.
> > > 
> > > Can you try this version?  The IFF_DRV_OACTIVE bits don't look correct to me 
> > > so I've left them out.  I also changed the driver to use bus_*() vs 
> > > bus_space_*().
> > > 
> > > -- 
> > > John Baldwin
> > 
> > Tried it at home, worked great. My university's wireless is shoddy.
> 
> I'm not sure if this is related to your patch or not, but I've been
> getting spurts of kernel: stray irq7 messages that I don't recall
> getting before the patch. Do you think it could be related?

I'm not sure.  Presumably your an(4) adapter isn't using IRQ 7?  I will
commit the current set of patches, but perhaps it is worth trying the
changes for OACTIVE.  Hmm, it does seem that the OACTIVE handling is a bit
busted as the current code will never set the flag since m0 is always NULL
when the function is exited.  I still don't think the DFly change is correct
since it can set the flag if the ifqueue was empty for some reason.  Perhaps
try this patch, it sets OACTIVE if we queued any packets for transmit:

Index: if_an.c
===================================================================
--- if_an.c	(revision 199757)
+++ if_an.c	(working copy)
@@ -2915,11 +2915,11 @@
 		CSR_WRITE_2(sc, AN_INT_EN(sc->mpi350), AN_INTRS(sc->mpi350));
 	}
 
-	if (m0 != NULL)
+	if (sc->an_rdata.an_tx_prod != idx) {
 		ifp->if_drv_flags |= IFF_DRV_OACTIVE;
+		sc->an_rdata.an_tx_prod = idx;
+	}
 
-	sc->an_rdata.an_tx_prod = idx;
-
 	return;
 }
 


-- 
John Baldwin
From david.somayajulu at qlogic.com  Tue Nov 24 21:37:10 2009
From: david.somayajulu at qlogic.com (David Somayajulu)
Date: Tue Nov 24 21:37:16 2009
Subject: dev/ixgb and dev/ixgbe
Message-ID: <75E1A2A7D185F841A975979B0906BBA671F9B39870@AVEXMB1.qlogic.org>

Hi All,
I would really appreciate if someone can help me understand the difference between the above drivers from Intel. Is one of them for older hardware ?

thanks
david S.
From imp at bsdimp.com  Tue Nov 24 22:10:45 2009
From: imp at bsdimp.com (M. Warner Losh)
Date: Tue Nov 24 22:10:51 2009
Subject: dev/ixgb and dev/ixgbe
In-Reply-To: <75E1A2A7D185F841A975979B0906BBA671F9B39870@AVEXMB1.qlogic.org>
References: <75E1A2A7D185F841A975979B0906BBA671F9B39870@AVEXMB1.qlogic.org>
Message-ID: <20091124.150636.1649828700.imp@bsdimp.com>

In message: <75E1A2A7D185F841A975979B0906BBA671F9B39870@AVEXMB1.qlogic.org>
            David Somayajulu <david.somayajulu@qlogic.com> writes:
: I would really appreciate if someone can help me understand the
: difference between the above drivers from Intel. Is one of them for
: older hardware ?

>From their respective man pages:

ixgb:
     The ixgb driver provides support for PCI Gigabit Ethernet adapters based
     on the Intel 82597EX Ethernet controller chips.  The driver supports
     Transmit/Receive checksum offload and Jumbo Frames.

ixgbe:
     The ixgbe driver provides support for PCI 10Gb Ethernet adapters based on
     the Intel 82598EB Intel(R) Network Connections.  The driver supports
     Jumbo Frames, MSIX, TSO, and RSS.

Warner

From manoj.shar at gmail.com  Tue Nov 24 22:14:39 2009
From: manoj.shar at gmail.com (Manoj Sharma)
Date: Tue Nov 24 22:14:45 2009
Subject: dev/ixgb and dev/ixgbe
In-Reply-To: <75E1A2A7D185F841A975979B0906BBA671F9B39870@AVEXMB1.qlogic.org>
References: <75E1A2A7D185F841A975979B0906BBA671F9B39870@AVEXMB1.qlogic.org>
Message-ID: <d6dada100911241351u1e8a81a6xe0b0f155386eb942@mail.gmail.com>

ixgb is for Intel 82597 while ixgbe for 82598.

On Tue, Nov 24, 2009 at 1:23 PM, David Somayajulu <
david.somayajulu@qlogic.com> wrote:

> Hi All,
> I would really appreciate if someone can help me understand the difference
> between the above drivers from Intel. Is one of them for older hardware ?
>
> thanks
> david S.
> _______________________________________________
> freebsd-drivers@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
> To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org"
>
From ander at angels.org.ua  Tue Nov 24 22:15:22 2009
From: ander at angels.org.ua (Ander)
Date: Tue Nov 24 22:15:30 2009
Subject: dev/ixgb and dev/ixgbe
In-Reply-To: <75E1A2A7D185F841A975979B0906BBA671F9B39870@AVEXMB1.qlogic.org>
References: <75E1A2A7D185F841A975979B0906BBA671F9B39870@AVEXMB1.qlogic.org>
Message-ID: <61a6e18f0911241343v619b8b4cq1aa2610a987ecf4e@mail.gmail.com>

Hi!

> I would really appreciate if someone can help me understand the difference between the above drivers from Intel. Is one of them for older hardware ?

They support different chipsets.

You can try to use "man" ;)


The ixgb driver provides support for PCI Gigabit Ethernet adapters based
     on the Intel 82597EX Ethernet controller chips.

 The ixgbe driver provides support for PCI 10Gb Ethernet adapters based on
     the Intel 82598EB Intel(R) Network Connections.


-- 
Andriy Radyk aka Ander aka Ender