; -Ben
>
>
>
> *From:* discuss-gnuradio-bounces+blapointe=ll.mit@gnu.org [mailto:
> discuss-gnuradio-bounces+blapointe=ll.mit@gnu.org] *On Behalf Of *Robert
> McGwier
> *Sent:* Monday, April 28, 2014 7:26 AM
> *To:* Marcus D. Leech
> *Cc:* Discuss-gnuradio@gnu.o
Hi all -
Just to clarify, it isn't the *version of OS* that matters, but rather
the *version
of the kernel provided by the OS*, that matters.
At the top of our instructions for installing the USRP RIO kernel module,
it lists the maximum kernel version we currently support:
"*NOTE: The latest sup
[mailto:discuss-gnuradio-bounces+blapointe=ll.mit@gnu.org] On Behalf Of
Robert McGwier
Sent: Monday, April 28, 2014 7:26 AM
To: Marcus D. Leech
Cc: Discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] X300 PCIe issues
It needed to be said, but my only goal is to
ACCEPT AND LOVE 10GigE
It needed to be said, but my only goal is to
ACCEPT AND LOVE 10GigE until and unless you demand the low latency afforded
by the PCIe interface. The things I am working on demand that we meet the
tight timing requirements of open specification waveforms. PCIe was
required. The x3x0 series are m
Hi,
> So, would we accept an applications-layer API that changed roughly every two
> months? I would argue, no, we wouldn't. But
> people developing in kernel land seem to accept it as some kind of
> necessary gospel.
For the kernel, the "application layer API" is the user space
interface an
On 04/27/2014 05:32 PM, Sylvain Munaut wrote:
While the "top side" API is
very stable so that applications hardly *ever* experience API changes
that require on-going tedious maintenance, the same cannot be said of code
that runs in the kernel. Quite the contrary. Linus and friends
*routine
> While the "top side" API is
> very stable so that applications hardly *ever* experience API changes
> that require on-going tedious maintenance, the same cannot be said of code
> that runs in the kernel. Quite the contrary. Linus and friends
> *routinely and regularly* change critical APIs w
On 04/27/2014 02:45 PM, Robert McGwier wrote:
Backing off to Ubuntu 12.04.4 LTS was successful in getting the PCIe
Express interface to build, dkms the kernel module, start and
uhd_find_device sees the USRP x300.
Now for the fun part using it.
Finally:
To all those entertaining PCIe inte
Backing off to Ubuntu 12.04.4 LTS was successful in getting the PCIe
Express interface to build, dkms the kernel module, start and
uhd_find_device sees the USRP x300.
Now for the fun part using it.
Finally:
To all those entertaining PCIe interfacing, do not install a later version
of kernel
Tim and I are going to swap back to 12.04.4 LTS. I suggest that some note
to the installation for x3x0 say which versions of Ubuntu, kernels, etc.
are supported currently.
Thanks for your time.
Bob
On Sat, Apr 26, 2014 at 12:01 PM, Robert McGwier wrote:
> Okay, I thought that was it. I will
Okay, I thought that was it. I will back off to 13.XX LTS for now.
Bob
On Fri, Apr 25, 2014 at 6:28 PM, Matt Ettus wrote:
> You are using ubuntu 14.4 which has a new kernel. It will take us a
> little while to get our kernel module working with it. In the mean time,
> going to an older k
You are using ubuntu 14.4 which has a new kernel. It will take us a
little while to get our kernel module working with it. In the mean time,
going to an older kernel or distribution will fix it. This does not
affect ethernet connections.
Matt
On Apr 25, 2014 11:38 PM, "Robert McGwier" wrote
I have my new x300's. The NI ExpressCard-8360B is recognized by my Intel
5, Lenovo, 64 bit machine running U 14.04 LTS.
I naively assumed that given the way things had gone before, that this
would be a low impact out of the box experience. uhd_find_devices finds
nothing.
So I go and dig and fin
13 matches
Mail list logo
