On Sun, Mar 31, 2013 at 2:00 PM, <xen-arm-request@lists.xen.org> wrote:
> Send Xen-arm mailing list submissions to
> xen-arm@lists.xen.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm
> or, via email, send a message with subject or body 'help' to
> xen-arm-request@lists.xen.org
>
> You can reach the person managing the list at
> xen-arm-owner@lists.xen.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Xen-arm digest..."
>
>
> Today's Topics:
>
> 1. Questions on Xen Back end and front end drivers (akshay st)
> 2. Questions on Xen Back end and front end drivers (akshay st)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 31 Mar 2013 19:47:39 +0800 (SGT)
> From: akshay st <akshayts@yahoo.co.in>
> To: "xen-arm@lists.xen.org" <xen-arm@lists.xen.org>
> Subject: [XenARM] Questions on Xen Back end and front end drivers
> Message-ID:
> <1364730459.65126.YahooMailNeo@web190703.mail.sg3.yahoo.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
> I read that DOM0 implements and handles all device drivers. All Domu's
> access device driver through DOM0, For this back end and front end drivers
> were created?. Just for understanding i was going? through Linux XEN Block
> back end and front end driver.(xen-blkfront.c), I am not sure but i see
> that there no real device involved in frontend and backend communication?
> How does it boil down to Real device. What is the use of XEN Block back end
> and front end drivers since there communication happens only thru Memory ?.
>
>
> For example i have a MTD Nand device which DOM0 should implement
> completely?.
>
> How can other Domains access this MTD Device I guess we have to have a MTD
> Back end driver for DOM0 and front end drivers for DOM U's?
>
>
> My understanding is Back end drivers should do hardware specific tasks?.
> Any good reference to understand backend and front end would be of great
> help.
>
>
> Warm Regards,
> Akshay
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.xen.org/archives/html/xen-arm/attachments/20130331/ac191ced/attachment.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Sun, 31 Mar 2013 19:53:59 +0800 (SGT)
> From: akshay st <akshayts@yahoo.co.in>
> To: "xen-arm@lists.xen.org" <xen-arm@lists.xen.org>
> Subject: [XenARM] Questions on Xen Back end and front end drivers
> Message-ID:
> <1364730839.79628.YahooMailNeo@web190704.mail.sg3.yahoo.com>
> Content-Type: text/plain; charset=iso-8859-1
>
> ---- Resending in Plain message format? -----
>
>
> Hi,
>
> I read that DOM0 implements and handles all device drivers. All Domu's
> access device driver through DOM0, For this back end and front end
> drivers were created?. Just for understanding i was going? through Linux
> XEN Block back end and front end driver.(xen-blkfront.c), I am not sure but
> i see that there no real device involved in frontend and backend
> communication? How does it boil down to Real device. What is the use of
> XEN Block back end and front end drivers since there communication
> happens only thru Memory ?.
>
>
> For example i have a MTD Nand device which DOM0 should implement
> completely?.
>
> How can other Domains access this MTD Device I guess we have to have a MTD
> Back end driver for DOM0 and front end drivers for DOM U's?
>
>
> My understanding is Back end drivers should do hardware specific tasks?.
> Any good reference to understand backend and front end would be of great
> help.
>
>
> Warm Regards,
> Akshay
>
>
>
> ------------------------------
>
> _______________________________________________
> Xen-arm mailing list
> Xen-arm@lists.xen.org
> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm
>
>
> End of Xen-arm Digest, Vol 53, Issue 12
> ***************************************
>
> Send Xen-arm mailing list submissions to
> xen-arm@lists.xen.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm
> or, via email, send a message with subject or body 'help' to
> xen-arm-request@lists.xen.org
>
> You can reach the person managing the list at
> xen-arm-owner@lists.xen.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Xen-arm digest..."
>
>
> Today's Topics:
>
> 1. Questions on Xen Back end and front end drivers (akshay st)
> 2. Questions on Xen Back end and front end drivers (akshay st)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 31 Mar 2013 19:47:39 +0800 (SGT)
> From: akshay st <akshayts@yahoo.co.in>
> To: "xen-arm@lists.xen.org" <xen-arm@lists.xen.org>
> Subject: [XenARM] Questions on Xen Back end and front end drivers
> Message-ID:
> <1364730459.65126.YahooMailNeo@web190703.mail.sg3.yahoo.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
> I read that DOM0 implements and handles all device drivers. All Domu's
> access device driver through DOM0, For this back end and front end drivers
> were created?. Just for understanding i was going? through Linux XEN Block
> back end and front end driver.(xen-blkfront.c), I am not sure but i see
> that there no real device involved in frontend and backend communication?
> How does it boil down to Real device. What is the use of XEN Block back end
> and front end drivers since there communication happens only thru Memory ?.
>
>
> For example i have a MTD Nand device which DOM0 should implement
> completely?.
>
> How can other Domains access this MTD Device I guess we have to have a MTD
> Back end driver for DOM0 and front end drivers for DOM U's?
>
>
> My understanding is Back end drivers should do hardware specific tasks?.
> Any good reference to understand backend and front end would be of great
> help.
>
>
> Warm Regards,
> Akshay
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.xen.org/archives/html/xen-arm/attachments/20130331/ac191ced/attachment.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Sun, 31 Mar 2013 19:53:59 +0800 (SGT)
> From: akshay st <akshayts@yahoo.co.in>
> To: "xen-arm@lists.xen.org" <xen-arm@lists.xen.org>
> Subject: [XenARM] Questions on Xen Back end and front end drivers
> Message-ID:
> <1364730839.79628.YahooMailNeo@web190704.mail.sg3.yahoo.com>
> Content-Type: text/plain; charset=iso-8859-1
>
> ---- Resending in Plain message format? -----
>
>
> Hi,
>
> I read that DOM0 implements and handles all device drivers. All Domu's
> access device driver through DOM0, For this back end and front end
> drivers were created?. Just for understanding i was going? through Linux
> XEN Block back end and front end driver.(xen-blkfront.c), I am not sure but
> i see that there no real device involved in frontend and backend
> communication? How does it boil down to Real device. What is the use of
> XEN Block back end and front end drivers since there communication
> happens only thru Memory ?.
>
>
> For example i have a MTD Nand device which DOM0 should implement
> completely?.
>
> How can other Domains access this MTD Device I guess we have to have a MTD
> Back end driver for DOM0 and front end drivers for DOM U's?
>
>
> My understanding is Back end drivers should do hardware specific tasks?.
> Any good reference to understand backend and front end would be of great
> help.
>
>
> Warm Regards,
> Akshay
>
>
>
> ------------------------------
>
> _______________________________________________
> Xen-arm mailing list
> Xen-arm@lists.xen.org
> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm
>
>
> End of Xen-arm Digest, Vol 53, Issue 12
> ***************************************
>