Hi Ayman, We've all been at a very busy Linaro Connect event in San Francisco, as Neil told you in a previous email, and I only just got back home an hour ago. I think you might be being a little unreasonable expecting a coherent response at this time. I'm back in the office on tuesday, and will deal with your response then.
Regards Dave Sent from my Aldis Lamp > On 3 Nov 2013, at 09:10, Ayman Hendawy <ayman.hend...@gmail.com> wrote: > > Hi, > > Kindly, could I get your reply on my previous e-mail. > > Thanks > > > >> On Fri, Nov 1, 2013 at 9:57 AM, Ayman Hendawy <ayman.hend...@gmail.com> >> wrote: >> Hi, >> >> Thanks for your detailed reply, >> I'm asking this question, because I was thinking about creating an open >> source Remote Embedded Lab, where developers have access to many open source >> kits(e.g, Panda, Beagle, Ethernut, etc.) remotely, plus remote access to >> the measurement tools in this lab (e.g, oscilloscope, Logic analyzer, etc.) >> connected to this kits, I think something like that will have a great impact >> on embedded system world especially open source software developers, every >> developer like to have his own lab, buying new kits& measurement tools is >> expensive. >> >> My preliminary thought is to give the user a full access to there remote >> kits, through Ethernet JTAG and other tools, where the user is responsible >> for every thing, burn the bootloader, program SD Card, the connection >> between the measurement tools and the kits can be done by many ways (like >> multiplexer) and to be configured through web interface. >> >> So I searched the web for a similar solution, providing H.W remote access, >> and I found your team, doing it but in a different way of may thought, so I >> need to understand the limitations and possibilities to doing so, if we give >> the user access to a full access via JTAGs is this may cause a problem to >> the kits. >> >> Now I hope you understand my full idea, kindly I would like to hear you >> suggestions to do so. >> >> Thanks >> >> >> >> >>> On Thu, Oct 31, 2013 at 7:37 PM, Dave Pigott <dave.pig...@linaro.org> wrote: >>> >>> On 31 Oct 2013, at 08:42, Neil Williams <codeh...@debian.org> wrote: >>> >>> > On Thu, 31 Oct 2013 09:14:47 +0200 >>> > Ayman Hendawy <ayman.hend...@gmail.com> wrote: >>> > >>> >> Dear Neil, >>> > >>> > Do not reply to individuals. Keep replies only to the list. >>> > >>> >> Actually I wonder why it's not more open, why I can't get a real time >>> >> access to the kit serial console, why debugger is not available, >>> >> suppose I have an application over OS, I need to debug my code using >>> >> a debugger, to get know the certain line causing the problem, why I >>> >> don't have an access to some of the kit peripherals like USB port by >>> >> some how. >>> >> >>> >> What I mean, such great effort of LAVA, what limit it to give there >>> >> users more deeply access to there kits? why it's limited to posting >>> >> jobs? >>> >>> To add to what Neil said: >>> >>> The LAVA lab farm, which is what validation.linaro.org gives access to, is >>> an automated test environment. The point of Linaro is to provide constantly >>> improving Linux distributions, and part of this effort is to test changes >>> automatically in LAVA - the Linaro Automated Validation Architecture. So >>> the lab is all about automation, not about free access to hardware. It is a >>> service that is only available to members and Linaro engineers. You have to >>> understand that we are a not-for-profit organisation that is funded by its >>> members. If we granted open access to the world, we would be giving the >>> potential for commercial competitors to gain access to advanced and >>> restricted hardware. >>> >>> Linaro is an Open Source Software company - and indeed every line of code >>> we generate is available freely and openly. We are not an Open Access >>> Hardware Service. >>> >>> If you are a Linaro assignee, or have a reason why you would need access >>> that our Technical Steering Committee (TSC) agree to, then we can grant you >>> access to be able to submit jobs into the Automated Validation framework, >>> to a subset of devices in the validation farm - some devices are restricted >>> because they are advanced hardware or emulations of silicon that have not >>> yet been made commercially available and our members would not be very >>> pleased if open access was granted. >>> >>> So, in summary, the action that you must take is to provide us with >>> information on why you need access to the LAVA farm and we will forward >>> this onto the Linaro TSC. >>> >>> Kind regards >>> >>> Dave Pigott >>> LAVA Lab Lead >> >> >> >> -- >> Best regards >> >> Ayman Hendawy >> Embedded system engineer >> http://www.linkedin.com/pub/ayman-hendawy/28/375/b5 >> >> Cairo,Egypt >> >> Phone: +201110406659 > > > > -- > Best regards > > Ayman Hendawy > Embedded system engineer > http://www.linkedin.com/pub/ayman-hendawy/28/375/b5 > > Cairo,Egypt > > Phone: +201110406659 > >
_______________________________________________ linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
