Nabble - freebsd-drivers

Regarding enabling IOAPIC on Intel Dual core processor based boards having Broadcom controller

2009-12-01T15:15:07Z

> Hi,
>
> We are using Freebsd6.2 bases OS on our LV 5200 Series
> Intel Dual Core Xeon bases processor(Wolfdale-DP-ULV). In
> the carrier board hosting the processor we have BCM5703
> controller.
> Currently we are using only one core in 32 bit mode and
> planning to use dual core where we need to enable IOAPIC.
> When IOAPIC is not enabled I see the bcm/bge driver is
> attached to IRQ10 and everything works fine, but when I
> enable IOAPIC I still see the boot msgs show that bge is
> attached to irq10 but the Broadcom controller does not come
> up. I found interrupt storm on irq17 ( remember without
> IOAPIC enable there are not IRQ assignments beyond
> IRQ16),looks like the controller is interrupting on 17 while
> driver waits on 10.
>
> When I stop and loader and assign it manually using
> config command "set hw.pci8.9.INTA.irq=”17”" ,
> everything works fine. Would be great if some one can throw
> some light on this IRQ mapping when IOAPIC is enabled and
> possible fix ( Software or BIOS?)
>
> NOTE: Other devices ( Intel controller (em driver)) are
> working fine only this BCM5703 is having issues with IOAPIC
>
> Thanks,
> Ravi
>
>
>
>

_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Regarding enabling IOAPIC on Intel Dual core processor based boards having Broadcom controller

2009-12-01T14:00:06Z

Hi,

We are using Freebsd6.2 bases OS on our LV 5200 Series Intel Dual Core Xeon
bases processor(Wolfdale-DP-ULV). In the carrier board hosting the processor
we have BCM5703 controller.
Currently we are using only one core in 32 bit mode and planning to use dual
core where we need to enable IOAPIC. When IOAPIC is not enabled I see the
bcm/bge driver is attached to IRQ10 and everything works fine, but when I
enable IOAPIC I still see the boot msgs show that bge is attached to irq10
but the Broadcom controller does not come up. I found interrupt storm on
irq17 ( remember without IOAPIC enable there are not IRQ assignments beyond
IRQ16),looks like the controller is interrupting on 17 while driver waits on
10.

When I stop and loader and assign it manually using config command "set
hw.pci8.9.INTA.irq=”17”" , everything works fine. Would be great if some one
can throw some light on this IRQ mapping when IOAPIC is enabled and possible
fix ( Software or BIOS?)

Thanks,
Ravi

--
Thanks,
Ravi
"The most influential person who will talk to you all day is you, so
you should be very careful about what you say to you!"
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

RE: dev/ixgb and dev/ixgbe

2009-11-30T11:02:39Z

Appreciate all your responses.
Thanks
david S.

-----Original Message-----
From: John Baldwin [mailto:jhb@...]
Sent: Monday, November 30, 2009 8:02 AM
To: freebsd-drivers@...
Cc: David Somayajulu
Subject: Re: dev/ixgb and dev/ixgbe

On Tuesday 24 November 2009 4:23:53 pm David Somayajulu 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 ?

I believe the short version is that ixgb(4) supports PCI-X 10gb adapters and
ixgbe(4) supports PCI-express 10gb adapters.

--
John Baldwin
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: dev/ixgb and dev/ixgbe

2009-11-30T08:02:09Z

On Tuesday 24 November 2009 4:23:53 pm David Somayajulu 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 ?

I believe the short version is that ixgb(4) supports PCI-X 10gb adapters and
ixgbe(4) supports PCI-express 10gb adapters.

--
John Baldwin
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Fix available for run driver

2009-11-28T02:06:07Z

Hello,

There are some fixes for run driver for 8.0 release and current. It can be downloaded from freebsd forums at
http://forums.freebsd.org/showpost.php?s=87e376cf71273061f7de5aaf258132a1&p=44110&postcount=1

Some packet loss/drop and memory leak have been identified and fixed. (It improved some performance, too)

Also, 40 more vender/device IDs have been added.

Details are on RELEASE_NOTES included.

Please update before the driver causing any troubles.

Akinori

__________________________________________________________________
Make your browsing faster, safer, and easier with the new Internet Explorer® 8. Optimized for Yahoo! Get it Now for Free! at http://downloads.yahoo.com/ca/internetexplorer/
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: dev/ixgb and dev/ixgbe

2009-11-24T14:06:36Z

In message: <75E1A2A7D185F841A975979B0906BBA671F9B39870@...>
David Somayajulu <david.somayajulu@...> 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

_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: dev/ixgb and dev/ixgbe

2009-11-24T13:51:07Z

ixgb is for Intel 82597 while ixgbe for 82598.

On Tue, Nov 24, 2009 at 1:23 PM, David Somayajulu <
david.somayajulu@...> 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@... mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
> To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."
>

Re: dev/ixgb and dev/ixgbe

2009-11-24T13:43:26Z

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
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

dev/ixgb and dev/ixgbe

2009-11-24T13:23:53Z

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@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: Cisco Aironet MPI350 Fix

2009-11-24T10:05:33Z

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
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: Cisco Aironet MPI350 Fix

2009-11-23T20:30:15Z

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?
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: Cisco Aironet MPI350 Fix

2009-11-23T13:39:46Z

In message: <20091123203008.GA26284@archimedes>
"Jeremy O'Brien" <obrien654j@...> 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
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: Cisco Aironet MPI350 Fix

2009-11-23T13:17:34Z

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.
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: Cisco Aironet MPI350 Fix

2009-11-23T12:25:46Z

On Mon, Nov 23, 2009 at 10:01:50AM -0500, John Baldwin wrote:

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?
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: Cisco Aironet MPI350 Fix

2009-11-23T07:01:50Z

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

_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Cisco Aironet MPI350 Fix

2009-11-22T09:55:55Z

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

_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: Support for VT2020

2009-11-17T14:13:54Z

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@...>
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/
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: Driver code release

2009-11-13T07:20:17Z

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@...>:

> On 2009-11-12 10:24:18 (-0500), John Baldwin <jhb@...> 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@...
>

Re: Support for VT2020

2009-11-13T01:25:50Z

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
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: Support for VT2020

2009-11-13T01:19:57Z

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.
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: Support for VT2020

2009-11-13T00:43:03Z

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
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: Support for VT2020

2009-11-12T23:19:34Z

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@...>
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.
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: Support for VT2020

2009-11-12T14:58:22Z

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
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: Support for VT2020

2009-11-12T14:30:08Z

My dmesg.boot file in attachment...

Janis

On Thu, 12 Nov 2009 23:15:56 +0200, Alexander Motin <mav@...>
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/

_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

dmesg.boot (85K) Download Attachment

Re: Support for VT2020

2009-11-12T13:15:56Z

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
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: Support for VT2020

2009-11-12T12:43:11Z

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@...>
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/
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: Driver code release

2009-11-12T11:42:05Z

Le Wed, 11 Nov 2009 14:47:06 +0000,
Brendan Kennedy <brendan.kennedy@...> 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.
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: Support for VT2020

2009-11-12T11:00:20Z

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
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: Driver code release

2009-11-12T07:35:59Z

On 2009-11-12 10:24:18 (-0500), John Baldwin <jhb@...> 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-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: Support for VT2020

2009-11-12T07:26:08Z

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
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: Driver code release

2009-11-12T07:24:18Z

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
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Support for VT2020

2009-11-12T02:24:37Z

Hello!

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

BR
Jānis
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Driver code release

2009-11-11T06:47:06Z

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
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: finished run driver for CURRENT

2009-11-08T21:44:52Z

----- 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/
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."

Re: finished run driver for CURRENT

2009-11-08T07:11:37Z

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@... mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@..."
>
>
>
>

--
He who laughs last hasn't been told the terrible truth.
_______________________________________________
freebsd-drivers@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@..."