On 05/02/14 23:21, Michael Kenney wrote:
On Wed, Feb 5, 2014 at 1:38 PM, Michael Kenney mfken...@gmail.com wrote:
On Wed, Feb 5, 2014 at 1:22 PM, Martyn Welch mar...@welchs.me.uk wrote:
On 5 February 2014 17:41, Greg KH gre...@linuxfoundation.org wrote:
On Tue, Feb 04, 2014 at
On Tue, Feb 04, 2014 at 06:34:13PM +, Martyn Welch wrote:
On 04/02/14 16:34, Michael Kenney wrote:
Hi Martyn,
On Tue, Feb 4, 2014 at 7:28 AM, Martyn Welch martyn.we...@ge.com
mailto:martyn.we...@ge.com wrote:
On 28/12/13 00:34, Michael Kenney wrote:
Hi Martyn,
On Wed, Feb 5, 2014 at 1:22 PM, Martyn Welch mar...@welchs.me.uk wrote:
On 5 February 2014 17:41, Greg KH gre...@linuxfoundation.org wrote:
On Tue, Feb 04, 2014 at 06:34:13PM +, Martyn Welch wrote:
On 04/02/14 16:34, Michael Kenney wrote:
Hi Martyn,
On Tue, Feb 4, 2014 at 7:28
On Wed, Feb 5, 2014 at 1:38 PM, Michael Kenney mfken...@gmail.com wrote:
On Wed, Feb 5, 2014 at 1:22 PM, Martyn Welch mar...@welchs.me.uk wrote:
On 5 February 2014 17:41, Greg KH gre...@linuxfoundation.org wrote:
On Tue, Feb 04, 2014 at 06:34:13PM +, Martyn Welch wrote:
On 04/02/14
On 28/12/13 00:34, Michael Kenney wrote:
Hi Martyn,
On Fri, Dec 27, 2013 at 4:23 PM, Martyn Welch mar...@welchs.me.uk wrote:
On 27/12/13 20:15, Michael Kenney wrote:
We are using the vme_tsi148 bridge driver along with the vme_user
driver to access the VME boards. The A/D board requires D32
On 04/02/14 16:34, Michael Kenney wrote:
Hi Martyn,
On Tue, Feb 4, 2014 at 7:28 AM, Martyn Welch martyn.we...@ge.com
mailto:martyn.we...@ge.com wrote:
On 28/12/13 00:34, Michael Kenney wrote:
Hi Martyn,
On Fri, Dec 27, 2013 at 4:23 PM, Martyn Welch
On 14/01/14 04:07, Michael Kenney wrote:
Unfortunately, the results are the same. I'm running this from home so
I'll have to confirm with the logic-analyzer tomorrow but the bridge
driver error messages suggest the same D8 writes (which for some
reason our A/D board does not like).
The
On Tue, Jan 14, 2014 at 1:39 AM, Martyn Welch martyn.we...@ge.com wrote:
On 14/01/14 04:07, Michael Kenney wrote:
Unfortunately, the results are the same. I'm running this from home so
I'll have to confirm with the logic-analyzer tomorrow but the bridge
driver error messages suggest the same
On 07/01/14 16:14, Michael Kenney wrote:
Hi Martyn,
On Fri, Dec 27, 2013 at 4:34 PM, Michael Kenney mfken...@gmail.com wrote:
Hi Martyn,
On Fri, Dec 27, 2013 at 4:23 PM, Martyn Welch mar...@welchs.me.uk wrote:
On 27/12/13 20:15, Michael Kenney wrote:
We are using the vme_tsi148 bridge
Hi Martyn,
On Mon, Jan 13, 2014 at 4:00 AM, Martyn Welch martyn.we...@ge.com wrote:
[snip]
Hi Mike,
I'm a little bemused by this one - I haven't managed to replicate it yet. I
have a feeling that the VME driver in version 3.2 won't use 16-bit transfers
at the beginning of blocks that aren't
Hi Martyn,
On Mon, Jan 13, 2014 at 6:49 AM, Michael Kenney mfken...@gmail.com wrote:
Hi Martyn,
On Mon, Jan 13, 2014 at 4:00 AM, Martyn Welch martyn.we...@ge.com wrote:
[snip]
Hi Mike,
I'm a little bemused by this one - I haven't managed to replicate it yet. I
have a feeling that the
Hello,
I'm in the process of trying to debug an issue with a VME A/D board
and have noticed some curious behavior in the VME bus protocol.
We are using the vme_tsi148 bridge driver along with the vme_user
driver to access the VME boards. The A/D board requires D32 bus cycles
and the VME master
On 27/12/13 20:15, Michael Kenney wrote:
We are using the vme_tsi148 bridge driver along with the vme_user
driver to access the VME boards. The A/D board requires D32 bus cycles
and the VME master window is configured accordingly, however, when
monitoring the bus cycles with a logic analyzer, we
Hi Martyn,
On Fri, Dec 27, 2013 at 4:23 PM, Martyn Welch mar...@welchs.me.uk wrote:
On 27/12/13 20:15, Michael Kenney wrote:
We are using the vme_tsi148 bridge driver along with the vme_user
driver to access the VME boards. The A/D board requires D32 bus cycles
and the VME master window is
14 matches
Mail list logo
