Hi, I have followed the instructions on the https://devel.rtems.org/wiki/Developer/Simulators/QEMU#Usingthertems-testingModule
But each time I run the pc386 simscript, I get the message on the console tcg doesn't support requested feature:cpuid.01h.edx.vme[bit 1] and then nothing happens, I do not get any output. Can someone resolve this error? On Fri, Mar 4, 2016 at 8:08 PM, Gedare Bloom <ged...@rtems.org> wrote: > The quickest way to get started is to follow the directions at > > https://devel.rtems.org/wiki/Developer/Simulators/QEMU#Usingthertems-testingModule > > you can use the rtems-source-builder/bare/devel/qemu.bset to compile qemu. > > On Thu, Mar 3, 2016 at 10:30 PM, Sambeet Panigrahi > <sambeet161...@gmail.com> wrote: > > Thank you. I would still like to continue with my work with Rock because > I > > like it and the experience would help. > > So I did not get your previous answer.How am I supposed to run the build > > conf?Qemu is an emulator so I can run it on my system and then emulate > > i386-rtems/pc486 BSP and then try running Rock on it. > > > > https://devel.rtems.org/wiki/Developer/Simulators/QEMU > > > > Can you be a little more elaborate please? > > > > On Thu, Mar 3, 2016 at 12:54 PM, Sambeet Panigrahi > > <sambeet161...@gmail.com> wrote: > >> This is not an open project. But Joel has suggested for a ROS port.Will > >> that > >> be a feasible project for GSoC-2016? Is RTEMS community interested for a > >> ROS > >> port if I can find co-mentors? > >> > >> On Mar 3, 2016 11:17 PM, "Gedare Bloom" <ged...@rtems.org> wrote: > >>> > >>> The IoT project is interesting, but it needs some additional fleshing > >>> out. I tend to agree with Sebastian's interpretation of the lack of > >>> interest from the Rock community will make it hard to complete a GSoC > >>> successfully. > >>> > >>> On Thu, Mar 3, 2016 at 10:19 AM, Sambeet Panigrahi > >>> <sambeet161...@gmail.com> wrote: > >>> > Hi, > >>> > I have had the opportunity of talking to Sebastian Huber. He does not > >>> > consider the porting of Rock on RTEMS as a suitable GSoC project.In > his > >>> > words > >>> > > >>> > "since the rock project seems to have no interest in RTEMS support I > >>> > don't > >>> > think this is a suitable GSoC project" > >>> > > >>> > I have made some progress in understanding CMake and rock libraries > for > >>> > the > >>> > purpose of the port. But the fact is the replies have been really > late. > >>> > It > >>> > is true to some extent. Should I reconsider the project? > >>> > If so, my next choice after Tiny RTEMS is the IOT project. How far do > >>> > you > >>> > think that is feasible? > >>> > Regards > >>> > Sambeet > >>> > > >>> > > >>> > On Thu, Feb 25, 2016 at 10:55 PM, Gedare Bloom <ged...@rtems.org> > >>> > wrote: > >>> >> > >>> >> There is no official work. If he has been answering questions, that > is > >>> >> good. You should work on creating a suitably complete proposal, and > >>> >> you should attempt to recreate the prior work as well as you can. We > >>> >> do not want you spending the first chunk of summer just getting to > the > >>> >> point that previous attempts got already. > >>> >> > >>> >> Gedare > >>> >> > >>> >> On Wed, Feb 24, 2016 at 1:28 PM, Sambeet Panigrahi > >>> >> <sambeet161...@gmail.com> wrote: > >>> >> > Hi, > >>> >> > I have talked with previous socis students and people from > dfki.They > >>> >> > are > >>> >> > all > >>> >> > ready to answer questions, but not hold any official position. I > >>> >> > have > >>> >> > contacted Martin Zenzes of dfki and he has been very helpful in > >>> >> > helping > >>> >> > me > >>> >> > to understand the project and I quote from his mail: > >>> >> > > >>> >> > "and lets say you can ask me anything, but i'm hesitant to fill > >>> >> > official > >>> >> > positions?" > >>> >> > > >>> >> > So will it solve the purpose.Does he need to apply for > co-mentoring > >>> >> > with > >>> >> > google or is there some official work involved? > >>> >> > > >>> >> > Rock co-mentor is not mandatory, but highly encouraged and will > >>> >> > improve your project's chances to be accepted and to be > successful. > >>> >> > You should reach out to the SOCIS student and mentors to see if > they > >>> >> > would be willing to co-mentor for GSoC. > >>> >> > > >>> >> > TinyRTEMS is not a great project currently as there are many > efforts > >>> >> > ongoing that make this a moving target. The most likely work to be > >>> >> > done is to fix the remaining linkcmds files (ld linker scripts) to > >>> >> > add > >>> >> > the right KEEP() directives so that our gcc per-function and > >>> >> > per-section optimizations work correctly. I don't see this as > >>> >> > sufficient for GSoC currently. > >>> >> > > >>> >> > Gedare > >>> >> > > >>> >> > On Sun, Feb 14, 2016 at 1:38 AM, Sambeet Panigrahi > >>> >> > <sambeet161...@gmail.com> wrote: > >>> >> >> I have been trying to reach potential co-mentors from the Rock > >>> >> >> community.However the response has not been that good. Is > >>> >> >> co-mentoring > >>> >> >> a > >>> >> >> compulsory condition? I also wanted to know if Tiny RTEMS project > >>> >> >> can > >>> >> >> be > >>> >> >> taken up as a GSoCproject this year. > >>> >> >> > >>> >> >> > >>> >> >> On Sat, Feb 13, 2016 at 8:25 AM, Gedare Bloom <ged...@rtems.org> > >>> >> >> wrote: > >>> >> >>> > >>> >> >>> You should try to get someone from the Rock or the Orocos > >>> >> >>> community > >>> >> >>> to > >>> >> >>> commit to (co-)mentor you if at all possible. > >>> >> >>> > >>> >> >>> On Fri, Feb 12, 2016 at 11:49 AM, Sambeet Panigrahi > >>> >> >>> <sambeet161...@gmail.com> wrote: > >>> >> >>> > Hi, > >>> >> >>> > I am interested in working on porting Rock on RTEMS. I am > >>> >> >>> > currently > >>> >> >>> > working > >>> >> >>> > on replicating Matthias Goldhoorn's work. I am also trying to > go > >>> >> >>> > through > >>> >> >>> > previous projects taken by Anna Vasquez for SOCIS. I wanted to > >>> >> >>> > know > >>> >> >>> > if > >>> >> >>> > this > >>> >> >>> > can be taken up as a project this year? > >>> >> >>> > > >>> >> >>> > Regards > >>> >> >>> > Sambeet > >>> >> >>> > > >>> >> >>> > _______________________________________________ > >>> >> >>> > devel mailing list > >>> >> >>> > devel@rtems.org > >>> >> >>> > http://lists.rtems.org/mailman/listinfo/devel > >>> >> >> > >>> >> >> > >>> > > >>> > >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
