Re: XVME 6300 with TSI148 bridge on 64 bit Debian (Linux 3.2.57) vme_user issue

2014-11-18 Thread Maurice Moss
Hi Martyn, Any update on this from your side? Cheers! On Mon, Nov 10, 2014 at 10:22 AM, Maurice Moss wrote: > Hi Martyn, > > Thanks for your reply. I have pasted the code below. It is very much > similar to your test code from the forum. > > Thanks! > > #define _XOPEN_

Re: XVME 6300 with TSI148 bridge on 64 bit Debian (Linux 3.2.57) vme_user issue

2014-11-10 Thread Maurice Moss
ster, Northants, NN12 6PF, United Kingdom > GE Intelligent Platforms Ltd > > GE imagination at work > > GE Intelligent Platforms Ltd, registered in England and Wales (3828642) at > 100 Barbirolli Square, Manchester, M2 3AB, VAT GB 927 5591 89 > > >> -Original

Re: XVME 6300 with TSI148 bridge on 64 bit Debian (Linux 3.2.57) vme_user issue

2014-11-07 Thread Maurice Moss
Hi Manohar/Dan, Any idea regarding this? Cheers, Maurice On Mon, Nov 3, 2014 at 5:25 PM, Maurice Moss wrote: > Hi Martyn, > > Thanks for your help from previous emails. I managed to talk to my > board using a VME-USB board. Now I am back to working with an SBC, and > I have a

Re: XVME 6300 with TSI148 bridge on 64 bit Debian (Linux 3.2.57) vme_user issue

2014-11-03 Thread Maurice Moss
2014 at 1:45 AM, Martyn Welch wrote: > On 23/07/14 03:09, Maurice Moss wrote: >> >> Hi Martyn, >> >> Thanks for your patience with me. I have a couple of questions for you: >> >> 0. I put the SBC with the right settings for Geographical addressing. >>

Re: XVME 6300 with TSI148 bridge on 64 bit Debian (Linux 3.2.57) vme_user issue

2014-07-22 Thread Maurice Moss
00 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 16 Memory at d000 (64-bit, non-prefetchable) [size=4K] Capabilities: Kernel driver in use: vme_tsi148 On Wed, Jul 16, 2014 at 12:47 AM, Martyn Welch wrote: > > > On 14/07/14 19:29, Maurice Moss

Re: XVME 6300 with TSI148 bridge on 64 bit Debian (Linux 3.2.57) vme_user issue

2014-07-14 Thread Maurice Moss
enabled [1.754942] vme_tsi148 :04:04.0: CR/CSR Offset: 0 [1.754948] vme_tsi148 :04:04.0: Enabling CR/CSR space Cheers! On Thu, Jul 3, 2014 at 8:18 AM, Maurice Moss wrote: > Martyn, > > OK. I feel like I am not clear. The kernel command line has a space, > but the line

Re: XVME 6300 with TSI148 bridge on 64 bit Debian (Linux 3.2.57) vme_user issue

2014-07-03 Thread Maurice Moss
Martyn, OK. I feel like I am not clear. The kernel command line has a space, but the line here in the email doesn't (I don't know how that happened). I am still stuck with the same issue. Sorry for all the confusion On Thu, Jul 3, 2014 at 8:15 AM, Maurice Moss wrote: > Yes, c

Re: XVME 6300 with TSI148 bridge on 64 bit Debian (Linux 3.2.57) vme_user issue

2014-07-03 Thread Maurice Moss
Yes, copy and paste issue, I had double checked that right after I sent you the mail. Sorry!! On Thu, Jul 3, 2014 at 3:47 AM, Martyn Welch wrote: > > > On 03/07/14 00:47, Maurice Moss wrote: >> >> I upgraded to linux kernel 3.14.9 (on Fedora). Re-compiled the kernel >&g

Re: XVME 6300 with TSI148 bridge on 64 bit Debian (Linux 3.2.57) vme_user issue

2014-07-02 Thread Maurice Moss
:04.0: Enabling CR/CSR space Any help is sincerely appreciated :) Cheers! On Tue, Jun 24, 2014 at 4:19 AM, Martyn Welch wrote: > On 23/06/14 16:05, Maurice Moss wrote: >> >> Hi All, >> >> Thanks for your reply. I have been away the last few weeks. >> >> Da

Re: XVME 6300 with TSI148 bridge on 64 bit Debian (Linux 3.2.57) vme_user issue

2014-06-23 Thread Maurice Moss
Cheers! On Wed, Jun 11, 2014 at 10:36 AM, Martyn Welch wrote: > Hi Maurice, > > > On 04/06/14 22:43, Maurice Moss wrote: >> >> Dear All, >> >> I came across the link here and decided to write to you, as I am >> facing a very similar problem: >>

XVME 6300 with TSI148 bridge on 64 bit Debian (Linux 3.2.57) vme_user issue

2014-06-04 Thread Maurice Moss
Dear All, I came across the link here and decided to write to you, as I am facing a very similar problem: http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2013-May/037941.html With the above linux, I have recompiled the kernel and booting the image with a vme_user.bus=0 vme_tsi14