2014-07-28T00:06:33 *** monstr has joined #rtems 2014-07-28T00:12:11 *** kiwichris has quit IRC (Ping timeout: 272 seconds) 2014-07-28T00:22:02 *** kiwichris has joined #rtems 2014-07-28T00:29:33 *** kiwichri_ has joined #rtems 2014-07-28T00:30:37 *** kiwichris has quit IRC (Read error: Connection reset by peer) 2014-07-28T00:31:02 *** kiwichris has joined #rtems 2014-07-28T00:34:59 *** kiwichri_ has quit IRC (Ping timeout: 272 seconds) 2014-07-28T00:44:27 *** kiwichri_ has joined #rtems 2014-07-28T00:45:07 *** kiwichris has quit IRC (Ping timeout: 272 seconds) 2014-07-28T00:46:54 *** kiwichri_ has quit IRC (Read error: Connection reset by peer) 2014-07-28T00:47:21 *** kiwichris has joined #rtems 2014-07-28T00:53:43 *** kiwichri_ has joined #rtems 2014-07-28T00:53:43 *** kiwichris has quit IRC (Read error: Connection reset by peer) 2014-07-28T01:00:46 *** kiwichris has joined #rtems 2014-07-28T01:04:45 *** kiwichri_ has quit IRC (Ping timeout: 272 seconds) 2014-07-28T01:22:45 *** Schoumi_ is now known as Schoumi 2014-07-28T02:05:40 *** zoso has joined #rtems 2014-07-28T03:02:50 *** kiwichris has quit IRC () 2014-07-28T03:17:49 *** kiwichris has joined #rtems 2014-07-28T06:34:31 lo all 2014-07-28T06:35:32 lo 2014-07-28T06:35:36 lo peerst 2014-07-28T06:35:43 drats forgot to change nicks 2014-07-28T06:36:09 :-) 2014-07-28T06:36:18 beng-nl: do we really need the PHY driver for ethernet on BB or is it just nice to have? 2014-07-28T06:36:48 not for the bsp to work & be merged 2014-07-28T06:36:51 as I understand Uboot initializees the PHY already 2014-07-28T06:37:01 I mean for Ethernet to work 2014-07-28T06:37:11 oh.. i see.. 2014-07-28T06:37:33 i don't fully understand all the ins & outs of phy & mii separation to be honest 2014-07-28T06:37:47 apparently the minix ethernet driver already relies on the uboot initialization 2014-07-28T06:37:54 which i didn't know 2014-07-28T06:38:01 well if the phy works for a first version don’t touch it? 2014-07-28T06:38:17 sounds good to me 2014-07-28T06:38:20 do you favor the minix driver or the FreeBSD one? 2014-07-28T06:38:43 if i do the porting (as i was planning at some point), the minix driver, because it's easy to understand (for me) 2014-07-28T06:38:54 ok 2014-07-28T06:38:54 other than that i don't have an opinion, the freebsd one might be more mature and featureful 2014-07-28T06:40:22 what is missing from the minix driver? 2014-07-28T06:40:37 nothing as far as i'm concerned 2014-07-28T06:40:49 well then :-) 2014-07-28T06:40:56 e.g. it uses irq's and dma 2014-07-28T06:41:08 multicast filtering? 2014-07-28T06:41:24 that i don't know 2014-07-28T06:41:33 are drivers supposed to do that? 2014-07-28T06:41:42 thats usually the feature left for later 2014-07-28T06:41:58 there is always multicas handling in the TCP/IP stack 2014-07-28T06:42:16 but for this to work you need to switch to promiscous 2014-07-28T06:42:30 ugh 2014-07-28T06:42:30 so thats the minimal feature in the driver to make multicast work 2014-07-28T06:42:39 aha yeah 2014-07-28T06:42:57 most NICs have a hashtable to help pre filter multicast 2014-07-28T07:15:24 *** atgreen has quit IRC (Remote host closed the connection) 2014-07-28T08:22:12 *** Schoumi has quit IRC (Ping timeout: 250 seconds) 2014-07-28T08:24:19 *** Schoumi has joined #rtems 2014-07-28T09:27:36 *** monstr has quit IRC (Remote host closed the connection) 2014-07-28T09:37:26 *** Hesham has joined #rtems 2014-07-28T10:02:39 *** zoso has quit IRC (Quit: Leaving) 2014-07-28T10:32:22 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-28T11:14:23 *** Hesham has quit IRC (Ping timeout: 264 seconds) 2014-07-28T11:31:43 *** Hesham has joined #rtems 2014-07-28T12:13:23 *** atgreen has joined #rtems 2014-07-28T13:38:14 *** Hesham has quit IRC (Quit: Leaving.) 2014-07-28T13:59:27 *** peerst has quit IRC (Quit: peerst) 2014-07-28T14:02:01 *** peerst has joined #rtems 2014-07-28T16:31:57 *** kiwichris has quit IRC () 2014-07-28T16:49:16 *** kiwichris has joined #rtems 2014-07-28T17:56:08 *** edwardk has joined #rtems 2014-07-28T20:10:40 *** gigetoo has quit IRC (Remote host closed the connection) 2014-07-28T20:44:08 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-28T21:00:54 *** edwardk has joined #rtems 2014-07-28T21:58:43 *** Hesham has joined #rtems 2014-07-29T00:22:19 *** monstr has joined #rtems 2014-07-29T00:54:22 *** Hesham has quit IRC (Ping timeout: 245 seconds) 2014-07-29T01:04:41 *** monstr has quit IRC (Remote host closed the connection) 2014-07-29T01:08:13 *** zoso has joined #rtems 2014-07-29T01:09:23 *** Hesham has joined #rtems 2014-07-29T01:50:13 *** kiwichris has quit IRC () 2014-07-29T02:03:48 *** monstr has joined #rtems 2014-07-29T02:04:06 *** kiwichris has joined #rtems 2014-07-29T02:17:34 Hesham, hi 2014-07-29T02:18:06 Hi kiwichris, I was replying to your e-mail 2014-07-29T02:18:27 I did wonder. Chatting here ok ? 2014-07-29T02:18:32 Sure 2014-07-29T02:18:51 Regarding or1k and newlib version... 2014-07-29T02:18:56 Sorry about changing the rtems-gcc-4.8.2 stuff. 2014-07-29T02:19:14 Our newlib patch that adds openrisc support to newlib has been merged with upstream by Jul 18, so any newlib-cvs version before that date will cause or1k bset not to be built correctly 2014-07-29T02:19:34 What changes? 2014-07-29T02:24:55 I am working on my local and fetched the new RSB updates 2014-07-29T02:25:11 Did not notice that rtems-or1k.bset has been updated 2014-07-29T02:25:20 deleted** 2014-07-29T02:25:50 I guess it was there before right? http://git.rtems.org/rtems-source-builder/tree/rtems/config/4.11 2014-07-29T02:26:36 or just at github? 2014-07-29T02:36:30 I did not delete it. 2014-07-29T02:36:36 Back soon. Need to move the care 2014-07-29T02:36:37 car 2014-07-29T02:36:40 *** kiwichris has quit IRC () 2014-07-29T02:47:14 *** kiwichris has joined #rtems 2014-07-29T02:47:53 kiwichris: Welcome back 2014-07-29T02:48:01 So, the rtems RSB git repo is not supposed to be synced with github RSB repo? Because or1k stuff only exists at github 2014-07-29T02:48:04 thanks. back at the office 2014-07-29T02:48:20 It should be sync'ed 2014-07-29T02:49:17 I have 'remote: 2: update github' in the messages for a push 2014-07-29T02:49:54 Could you please compare those for rtems-or1k.bset existance? 2014-07-29T02:49:54 http://git.rtems.org/rtems-source-builder/tree/rtems/config/4.11 2014-07-29T02:49:54 https://github.com/RTEMS/rtems-source-builder/tree/master/rtems/config/4.11 2014-07-29T02:50:25 I see it. 2014-07-29T02:50:40 https://github.com/RTEMS/rtems-source-builder/blob/master/rtems/config/4.11/rtems-or1k.bset 2014-07-29T02:51:08 By the way the "Tools configuration" should last in the file. 2014-07-29T02:51:25 Yes it's at github and not at rtems repo 2014-07-29T02:59:18 Oh I see. 2014-07-29T02:59:20 Sorry 2014-07-29T02:59:59 I have it in my repo 2014-07-29T03:00:29 This looks like a cgit issue 2014-07-29T03:01:10 $ git blame config/4.11/rtems-or1k.bset 2014-07-29T03:01:10 3a0e5615 (Hesham ALMatary 2014-05-26 03:40:22 +0200 1) # etc etc 2014-07-29T03:03:06 I have forked a vanilla repo again and found it.. weird.. 2014-07-29T03:03:41 kiwichris: Anyway, where should I redefine the newlib version to be able to build or1k gcc along with newlib-cvs ? 2014-07-29T03:04:13 I did this at the gcc-4.8.2-newlib-cvs-1 before 2014-07-29T03:06:42 The current is on the 26-Jul. Is that ok ? 2014-07-29T03:06:56 No 2014-07-29T03:07:03 12-Jul 2014-07-29T03:07:17 Why that date and not a later date ? 2014-07-29T03:07:34 Its 26-jul for gcc-4.8.2 2014-07-29T03:07:38 18-jul 2014-07-29T03:08:02 I have moved to 4.8.3. Can you move to that version as well ? 2014-07-29T03:08:52 I will see if the current gcc patch can apply for 4.8.3 and fix and issues, then I will move to 4.8.3 2014-07-29T03:09:07 any issues* 2014-07-29T03:10:18 thanks. I found none. 2014-07-29T03:12:35 Great, then it will build the tools again with the new hashes, and I will send you a patch once I make sure every thing works fine. 2014-07-29T03:14:06 thanks 2014-07-29T03:14:12 back soon 2014-07-29T03:14:33 *** kiwichris has quit IRC () 2014-07-29T03:40:23 *** kiwichris has joined #rtems 2014-07-29T03:55:05 *** kiwichris has quit IRC (Ping timeout: 252 seconds) 2014-07-29T04:16:44 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-29T04:21:18 *** kiwichris has joined #rtems 2014-07-29T04:22:52 *** kiwichris has quit IRC (Client Quit) 2014-07-29T04:27:49 *** kiwichris has joined #rtems 2014-07-29T04:28:49 *** edwardk has joined #rtems 2014-07-29T04:30:38 kiwichris, please find the latest e-mail with the RSB patch 2014-07-29T04:31:07 I have generated a new gcc-4.8.3 patch, and built the entire toolchain successfully 2014-07-29T04:39:04 Hesham, great and thanks. I am a little busy with somethings for a while but I will get it sorted when I can 2014-07-29T04:39:07 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-29T04:40:15 Take your time. 2014-07-29T05:51:35 *** JustJanek has joined #rtems 2014-07-29T06:09:26 *** xMYTHICx has joined #rtems 2014-07-29T06:42:40 *** edwardk has joined #rtems 2014-07-29T06:47:31 *** edwardk has quit IRC (Ping timeout: 255 seconds) 2014-07-29T06:57:50 *** atgreen has quit IRC (Remote host closed the connection) 2014-07-29T07:19:33 *** jenniferA has joined #rtems 2014-07-29T07:27:46 *** asuolen has joined #rtems 2014-07-29T07:29:44 *** edwardk has joined #rtems 2014-07-29T07:38:53 *** ker2x has joined #rtems 2014-07-29T07:38:57 friendly greeteings \o/ 2014-07-29T07:39:37 a friend suggested rtems to learn rtos 2014-07-29T07:44:20 i have some troubles finding documentation :) 2014-07-29T07:47:01 Good Morning :) http://www.rtems.org/onlinedocs/releases/rtemsdocs-4.10.2/share/rtems/html/ 2014-07-29T07:48:56 *** krzysiekm13 has joined #rtems 2014-07-29T07:49:43 thank you 2014-07-29T07:50:13 your welcome... also the wiki link on www.rtems.org will be helpful when just starting out. 2014-07-29T07:50:22 *** phipse has joined #rtems 2014-07-29T07:52:33 *** AoLaD has joined #rtems 2014-07-29T07:54:08 *** Sched has joined #rtems 2014-07-29T07:55:34 i'll install all the tools and try to run it on bochs 2014-07-29T07:58:33 *** JustJanek has joined #rtems 2014-07-29T08:02:43 hi 2014-07-29T08:02:49 Hi 2014-07-29T08:02:59 hello 2014-07-29T08:03:00 hi 2014-07-29T08:04:23 I'm not sure where gendare is but i already mailed him to ask to go first because i might have to go early/soon 2014-07-29T08:04:36 Hi, Gedare is going to be out this morning 2014-07-29T08:05:03 ooh 2014-07-29T08:05:13 Joel, may show up to lead, but I said I would if he doesn't make it 2014-07-29T08:05:14 yeah, i might have to go soon 2014-07-29T08:05:33 we can go ahead and start 2014-07-29T08:05:37 in that case can i just copy-paste what I've written? 2014-07-29T08:05:48 yes 2014-07-29T08:05:59 This week I have tried out ways to automate arinc653 header file inclusion to the build directory and made a new blog post about it. I also tried other arinc653 calls on rtems but I think I might have made a mistake on a previous blogpost on how the arinc653 calls are included to the static library of libpart.a so I might have to change that. So far I only found that arinc653 partition, arinc653 process and arinc653 time calls are included to the stat 2014-07-29T08:05:59 ic library and I was just at the point of trying to include arinc653 blackboard to the static library but it errored on a few files so I might have to notify the POK mailing list on missing headers. 2014-07-29T08:07:42 are blackboards in pok handled differently, then the other three? 2014-07-29T08:10:03 After flying over your blogpost: Is there a way to keep POK_PATH out of the RTEMS compile process? 2014-07-29T08:12:12 *** JustJanek has quit IRC (Ping timeout: 250 seconds) 2014-07-29T08:13:08 https://docs.google.com/document/d/1TvBHaCKfhqJNyiIdasGdab8cJMefVxIVK_e9prd1xv8/edit?usp=sharing 2014-07-29T08:13:39 hmm, there he goes :( 2014-07-29T08:13:42 Looks like we lost JustJanek 2014-07-29T08:14:13 lets go on to sched and we can pick back up JustJenek if he shows back up 2014-07-29T08:14:19 ok 2014-07-29T08:14:39 jenniferA: This is an old doc back to Jul 8 2014-07-29T08:14:58 Sched: are you there? 2014-07-29T08:15:04 Yes 2014-07-29T08:15:13 sorry: https://docs.google.com/document/d/1G1BegfoQ29hK2YlYnKwgzXDs1g-CwI_YdLU9yIBfLYA/edit?usp=sharing 2014-07-29T08:15:21 Thanks 2014-07-29T08:16:07 I drafted my presentation for today. 2014-07-29T08:16:15 Last week, I solve the problem of not handler interrupt in POK kernel. 2014-07-29T08:16:15 Then I start to write the receive mechanism in POK kernel. And I analysis the pok_sched and choose this functions end as the point to check interrupt. 2014-07-29T08:16:15 Then, I start to test and handling the interrupt. Here is the plan: 2014-07-29T08:16:15 1. Using the testHypercall to test the handler of timer interrupt, the testHypercall example is single partition and single thread. 2014-07-29T08:16:15 2. Build a new example, named partition-virtual-interrupt, imitating partition-threads example test the vCPU interrupt delivery when the partition switchs. 2014-07-29T08:16:16 3. test it in rtems-guest example, the handler of interrupt should be implementation in rtems, and pass it to POK kernel. 2014-07-29T08:16:26 jenniferA: please give us permissions to write to the doc 2014-07-29T08:18:05 What is that magic number 32 passed to your do_IRQ() function, mentioned in your blog? 2014-07-29T08:18:24 this is pit's irq number 2014-07-29T08:19:13 I was confused about how to manage irq in whole kernel, but finally I just leave it out for now. 2014-07-29T08:19:36 so your irqdesc table has vector numbers from 32 onwards to 48? 2014-07-29T08:19:56 No, this is not set. 2014-07-29T08:20:40 This is not fixed. 2014-07-29T08:21:14 please keep your github repo up to date, so we can have a look at your code, from the blogpost I am a bit confused 2014-07-29T08:21:37 so next week you are working on test cases, did I get that right? 2014-07-29T08:22:20 for example, if the guest OS register irq 34 first, then the first irq_desc.vector will be 34 2014-07-29T08:22:30 This part is up to date 2014-07-29T08:23:20 You can see the code in my github already, sorry I did not make a clear post 2014-07-29T08:23:50 Where confused you ? 2014-07-29T08:23:55 ah, ok, that way round. now i get it 2014-07-29T08:24:28 so you just send the IRQ to the vcpu and do the handling in the vcpu, when it is scheduled again? 2014-07-29T08:24:37 Yes, I will test, and make the mechanism of receive interrupt woke correctly. 2014-07-29T08:24:48 *work 2014-07-29T08:25:29 The receive part did not upload, because I just now test it. 2014-07-29T08:25:41 *not test it 2014-07-29T08:26:23 it is okay to upload work in progress, so we can have a look at it. 2014-07-29T08:26:24 I did not upload the receive part, so you can't handle it now. 2014-07-29T08:27:42 OK, but I am afraid if the approaching is not practicable, It will confused you. 2014-07-29T08:27:58 then you have to explain it to me ;) 2014-07-29T08:28:06 OK 2014-07-29T08:28:21 so what are you working on the next week? Test cases? 2014-07-29T08:28:59 And you can always write a how-it-should-work blog post 2014-07-29T08:29:04 yes, I'm sure the code is not workable for now. 2014-07-29T08:29:33 Did you agree to insert the receive function in pok_sched? 2014-07-29T08:30:14 Let's talk in private, 2014-07-29T08:30:35 otherwise the meeting will not end in time. 2014-07-29T08:30:49 we can switch to a private query, just sum up, what your goals for the next week are? 2014-07-29T08:31:05 The test case 2014-07-29T08:31:22 in the test case, make the code running. 2014-07-29T08:32:06 Please write a blog post about your experiences with the test cases, too. 2014-07-29T08:32:14 first is testHypercall, make sure the interrupt can be deliver correctly. 2014-07-29T08:32:39 OK, I will keep it in mind in testing. 2014-07-29T08:32:44 ok, jenniferA who is next? 2014-07-29T08:33:09 Asuolen can go next 2014-07-29T08:33:30 ok 2014-07-29T08:34:34 So this week I have ended the work on the SPI bus on the main RPI GPIO header 2014-07-29T08:35:50 Thank you very much. 2014-07-29T08:35:53 this was also tested with a SRAM device, using a minimal driver which transfer data sequentially (just to test the transfer of data through the bus) 2014-07-29T08:37:18 as far as this SPI bus goes I think it is finished (apart from small issues that I mentioned on the dev ML), the other two buses are internal ones, so they cannot be used with peripheral devices 2014-07-29T08:39:55 Sounds like good progress, do you have a plan for what is next? 2014-07-29T08:41:16 Sure. I will be working now on the I2C bus, and in the meantime I may improve the work on SPI (depending on received feedback) 2014-07-29T08:43:08 Another thing is that the access to the bus can also be made through DMA, but I have not seen any support for DMA on the RPI BSP, and so did not provide DMA access to the SPI bus (seems out of the scope of the proposed project) 2014-07-29T08:45:52 I think that is it from me, if there are no questions.. 2014-07-29T08:46:16 ok... Hesham you want to go next? 2014-07-29T08:46:22 Sure 2014-07-29T08:46:49 I have worked on fixing an issue with ticker.exe, specifically related to ISR handler. 2014-07-29T08:47:42 Did you find a solution, or is it still not working? 2014-07-29T08:47:46 ticker.exe is no working as expected, though printf does not work unless I make prink for test output 2014-07-29T08:48:00 Yes fixed.. 2014-07-29T08:48:59 I worked on a simple benchmark driver also, but I think OpenRISC limits timer driver capabilities as it has only one timer used currently for scheduling 2014-07-29T08:49:59 Also, I made some analysis regarding MMU and Caches for OpenRISC architecture. A simple manager can be implemented for or1ksim, but not fully-MMU featured. 2014-07-29T08:50:58 And the thing I did is generating RSB patches for referring to newlib-cvs and gcc-4.8.3, and adding the new RSB hash feature 2014-07-29T08:51:33 Next week, I will work on clean-up the code make some patches ready for review before merging it. 2014-07-29T08:52:27 great, it sounds like you made a lot of progress this week 2014-07-29T08:52:29 Besides, I will have to send a thread to the mailing list to make decision whether to continue development with or1ksim, or add a new HW BSP 2014-07-29T08:53:38 Thanks, I think that's all. 2014-07-29T08:53:53 thanks... AoLaD you want to go next? 2014-07-29T08:53:58 sure 2014-07-29T08:54:07 Hi JenniferA 2014-07-29T08:54:31 Last week I was working on my timer and interrupt driver. I have new consol driver prepared. I hope that compile-able version will be at github in the evening. My plans for the tomorrow are testing and debugging the new console driver. And if it will be functional I have two possibilities. Work on low level init (sync the cores and the memory of the procesor) or start to work on the LAN driver. 2014-07-29T08:55:01 one more option is to improve clock driver to support higher resolution 2014-07-29T08:55:28 I supose, I|ll see tomorow 2014-07-29T08:57:55 great, no problems? 2014-07-29T08:58:50 there are probably some. But nothing pops my mind right now 2014-07-29T08:59:38 ok.. we will look for the github update 2014-07-29T08:59:38 nothing critical 2014-07-29T08:59:50 sure 2014-07-29T09:00:58 If thats it we can move on to krzysiekm13 2014-07-29T09:01:02 thank you 2014-07-29T09:02:19 hi 2014-07-29T09:02:52 during this week I had to switch for a while to my master thesis - some deadlines are coming and I had to spend some time on it 2014-07-29T09:03:05 but I also made some progress 2014-07-29T09:03:47 I've cleaned up my code and added error handling code so now it terminates gracefully when some errors occurs 2014-07-29T09:04:09 I also improved final report generation 2014-07-29T09:04:31 it now looks much better and contains summary of analysis for each symbol subset 2014-07-29T09:04:51 I have code prepared to push to github and i will do this in the evening 2014-07-29T09:05:34 good... whats next? 2014-07-29T09:06:09 two things come to my mind: 2014-07-29T09:06:51 1st - symbol generation within covoar - Chris suggested covoar should be responsible for generating symbols for itself 2014-07-29T09:08:05 i don't know where to download the rpm for the cross compiler toolchain 2014-07-29T09:08:14 *** Sched has quit IRC () 2014-07-29T09:08:35 this is connected with determining how symbol sets should be specified - what should be the format of configuration file and should it be done by configuration file or maybe generated in some way automatically during each coverage run 2014-07-29T09:09:49 2nd - make running covoar in parallel, now i have it working as a single-thread and it takes quite a lot of time to run it several times in series, making it parallel should shorten the whole analysis time 2014-07-29T09:10:47 there is also an issue about qemu boot img for pc386 - where should it be stored or where should it be fetched from. It is not solved for now 2014-07-29T09:10:50 http://www.rtems.org/ftp/pub/gnucross/ ? 2014-07-29T09:11:09 i think this is all for now :) 2014-07-29T09:11:44 mmmmmm nope, wrong version, apparently 2014-07-29T09:11:45 damn 2014-07-29T09:11:57 ok .. thanks 2014-07-29T09:12:03 Did I miss anyone? 2014-07-29T09:12:40 perhaps ? 2014-07-29T09:15:22 ok ... meeting over 2014-07-29T09:15:35 *** Sched has joined #rtems 2014-07-29T09:15:47 *** krzysiekm13 has quit IRC (Quit: Page closed) 2014-07-29T09:15:53 ker2x: You may want to build from source see: http://www.rtems.org/ftp/pub/rtems/people/chrisj/source-builder/source-builder.html 2014-07-29T09:16:00 *** Sched has quit IRC (Client Quit) 2014-07-29T09:16:19 *** AoLaD has left #rtems 2014-07-29T09:18:15 i'm trying to follow the documentation :) 2014-07-29T09:18:16 which isn't easy 2014-07-29T09:23:44 mmmmmmm 2014-07-29T09:24:08 http://www.rtems.org/ftp/pub/rtems/people/chrisj/source-builder/source-builder.html#_build_sets a just get a tiny list 2014-07-29T09:24:34 and sparc isn't included in this list 2014-07-29T09:25:22 *** phipse has quit IRC (Quit: leaving) 2014-07-29T09:26:17 under the building section it describes how to build the sparc 2014-07-29T09:27:00 error: no build set file found: 4.11/rtems-sparc.bset 2014-07-29T09:27:03 *** edwardk has joined #rtems 2014-07-29T09:27:25 well i guess it's missing the whole "download rtems and install it here" 2014-07-29T09:29:04 if you follow the directions on setting the path and downloading the source builder this will build the tools. After the tools are built you can download and build rtems. 2014-07-29T09:29:44 i installed the dependencies (for ubuntu), git cloned source-builder 2014-07-29T09:30:21 sb-check is happy 2014-07-29T09:30:48 next step is --list-bsets 2014-07-29T09:31:05 and since nowhere in the doc it say to download and copy rtems somewhere, i didn't 2014-07-29T09:33:00 you don't have to download rtems till after you install the tools. did you cd to cd rtems-source-builder/rtems like the instructions say? 2014-07-29T09:34:59 heh 2014-07-29T09:34:59 thx 2014-07-29T09:35:17 sudenly magic happens :) 2014-07-29T09:35:29 *** zoso has quit IRC (Quit: Leaving) 2014-07-29T09:35:46 sorry about that :) 2014-07-29T09:36:04 now it download the sources :) 2014-07-29T09:55:54 *** jenniferA has quit IRC (Quit: Leaving) 2014-07-29T10:03:02 *** ker2x has quit IRC (Ping timeout: 240 seconds) 2014-07-29T10:16:23 *** ker2x has joined #rtems 2014-07-29T10:16:26 back 2014-07-29T10:16:36 make -j on qemu was a baaaaaaaaaaaaaaaaaad idea :) 2014-07-29T10:21:05 *** asuolen has quit IRC (Quit: Lost terminal) 2014-07-29T10:24:30 see you later 2014-07-29T10:24:32 *hugs* 2014-07-29T10:28:36 *** ppisa has joined #rtems 2014-07-29T10:28:43 *** ppisa has left #rtems ("Kopete 0.12.7 : http://kopete.kde.org") 2014-07-29T10:39:22 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-29T12:06:17 *** Hesham has quit IRC (Quit: Leaving.) 2014-07-29T12:52:27 *** edwardk has joined #rtems 2014-07-29T13:04:08 *** edwardk has quit IRC (Read error: Connection reset by peer) 2014-07-29T13:04:22 *** edwardk has joined #rtems 2014-07-29T13:12:38 *** monstr has quit IRC (Remote host closed the connection) 2014-07-29T13:42:30 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-29T13:47:14 *** edwardk has joined #rtems 2014-07-29T14:18:37 *** edwardk has quit IRC (Quit: Computer has gone to sleep.) 2014-07-29T15:10:35 *** edwardk has joined #rtems 2014-07-29T15:47:33 *** edwardk has quit IRC (Ping timeout: 240 seconds) 2014-07-29T16:52:57 *** edwardk has joined #rtems 2014-07-29T17:16:40 *** atgreen has joined #rtems 2014-07-29T18:17:01 *** edwardk_ has joined #rtems 2014-07-29T18:20:42 *** edwardk has quit IRC (Ping timeout: 250 seconds) 2014-07-29T18:21:33 *** edwardk_ has quit IRC (Ping timeout: 256 seconds) 2014-07-29T20:11:45 *** kiwichri_ has joined #rtems 2014-07-29T20:12:35 *** kiwichr__ has joined #rtems 2014-07-29T20:12:42 *** kiwichri_ has quit IRC (Read error: Connection reset by peer) 2014-07-29T20:14:39 *** kiwichr__ has quit IRC (Client Quit) 2014-07-29T20:15:05 *** kiwichris has quit IRC (Ping timeout: 272 seconds) 2014-07-29T20:34:28 *** kiwichris has joined #rtems 2014-07-29T21:15:14 *** edwardk has joined #rtems 2014-07-29T21:29:38 *** beng-nl has quit IRC (Ping timeout: 250 seconds) 2014-07-29T22:59:23 *** Hesham has joined #rtems 2014-07-30T00:16:20 *** monstr has joined #rtems 2014-07-30T00:20:33 *** monstr has quit IRC (Ping timeout: 240 seconds) 2014-07-30T00:34:00 *** monstr has joined #rtems 2014-07-30T01:31:44 *** zoso has joined #rtems 2014-07-30T03:11:57 *** guerby has quit IRC (Ping timeout: 256 seconds) 2014-07-30T03:25:07 'morning 2014-07-30T03:28:52 *** guerby has joined #rtems 2014-07-30T04:05:26 *** Sched has joined #rtems 2014-07-30T04:07:02 *** Sched has quit IRC (Client Quit) 2014-07-30T04:37:51 i'm at step 6.1 of source builder 2014-07-30T04:40:23 doesn't sound like a good idea because i don't understand this step :) 2014-07-30T04:42:33 i'm going to reread everything 2014-07-30T05:28:38 ker2x: what is the problem? 2014-07-30T06:12:04 no real problem 2014-07-30T06:12:15 i used source builder 2014-07-30T06:12:23 i have all the cross-compiling toolchain 2014-07-30T06:12:30 now i need to compile rtems 2014-07-30T06:13:03 if i understood correctly :) 2014-07-30T06:13:16 configure.ac:3: error: Autoconf version 2.69 or higher is required 2014-07-30T06:13:18 meh 2014-07-30T06:17:26 update your autconf, you should also decide which target you'd like to work on 2014-07-30T06:18:07 sparc 2014-07-30T06:20:10 i'm creating a docker container and try again :) 2014-07-30T06:20:29 Did you update your autoconf? 2014-07-30T06:20:47 i have the latest version i can get on my distro 2014-07-30T06:23:48 which is ubuntu 12.04LTS 2014-07-30T06:24:34 autoconf --version 2014-07-30T06:24:39 14.04 have 2.69 :) 2014-07-30T06:25:58 2.69 on 12.04 2014-07-30T06:26:07 sorry, 2.68 2014-07-30T06:31:44 building a docker container for rtems will be fun anyway 2014-07-30T06:38:32 *** ker2x has quit IRC (Read error: No route to host) 2014-07-30T06:40:04 *** Hesham has quit IRC (Quit: Leaving.) 2014-07-30T06:45:27 *** ker2x has joined #rtems 2014-07-30T06:45:35 meh, crash my laptop again 2014-07-30T06:46:36 Jul 30 13:34:55 arthurus kernel: [73232.432450] BUG: unable to handle kernel NULL pointer dereference at (null) 2014-07-30T06:46:39 doh 2014-07-30T06:51:32 ok, not docker :) 2014-07-30T07:11:02 *** atgreen has quit IRC (Ping timeout: 260 seconds) 2014-07-30T07:28:35 reboot 2014-07-30T07:28:36 brb 2014-07-30T07:28:39 *** ker2x has quit IRC (Quit: leaving) 2014-07-30T08:17:38 *** Hesham has joined #rtems 2014-07-30T09:08:40 *** Sched