2014-06-30T01:12:17 *** zoso has joined #rtems 2014-06-30T01:28:26 *** sebhub has joined #rtems 2014-06-30T02:12:59 *** mkhoory has quit IRC (Ping timeout: 264 seconds) 2014-06-30T04:34:08 *** cdesai has quit IRC (Read error: Connection reset by peer) 2014-06-30T06:33:27 *** zoso has quit IRC (Quit: Leaving) 2014-06-30T06:40:22 *** b47378 has joined #rtems 2014-06-30T06:50:36 hi 2014-06-30T06:51:17 Is there anybody here who could help me with a dynamic library loading issue? I have a basic dynamic library which should print "hello". When the library is loaded with dlopen(), the next message is returned: "global symbol nout found: puts". 2014-06-30T06:51:31 I compile it in a similar way as rtld test: 2014-06-30T06:51:32 arm-rtems4.11-ar -rcs libbasic_math.a basic_math.o 2014-06-30T06:51:32 rtems-ra --lib basic_math --output-path ./ --no-stdlibs --cc arm-rtems4.11-gcc -Wl,-static 2014-06-30T06:51:32 arm-rtems4.11-ar x libbasic_math.ra 2014-06-30T06:51:51 Do you have any suggestion? 2014-06-30T09:56:15 *** sebhub has quit IRC (Remote host closed the connection) 2014-06-30T10:37:25 *** atgreen has joined #rtems 2014-06-30T11:06:04 *** sorind has joined #rtems 2014-06-30T12:52:42 *** sorind has quit IRC (Quit: Leaving) 2014-06-30T13:08:55 *** atgreen has quit IRC (Ping timeout: 272 seconds) 2014-06-30T13:55:12 *** stryx` has quit IRC (Ping timeout: 245 seconds) 2014-06-30T13:56:35 *** stryx`_ has joined #rtems 2014-06-30T14:13:31 *** stryx`_ has quit IRC (Ping timeout: 272 seconds) 2014-06-30T16:01:33 *** kiwichris has joined #rtems 2014-06-30T16:18:36 *** kiwichris has quit IRC () 2014-06-30T16:39:17 *** kiwichris has joined #rtems 2014-06-30T17:02:25 *** kiwichris has quit IRC () 2014-06-30T17:06:43 *** kiwichris has joined #rtems 2014-06-30T19:09:57 *** mkhoory has joined #rtems 2014-06-30T19:26:24 *** mkhoory has quit IRC (Read error: Connection reset by peer) 2014-06-30T19:31:43 *** mkhoory has joined #rtems 2014-06-30T20:14:32 *** rokka has quit IRC (Ping timeout: 260 seconds) 2014-06-30T20:17:09 *** rokka has joined #rtems 2014-06-30T20:33:12 *** rokka has quit IRC (Ping timeout: 260 seconds) 2014-06-30T20:41:08 *** rokka has joined #rtems 2014-06-30T22:15:47 *** gigetoo has quit IRC (Remote host closed the connection) 2014-06-30T22:16:25 *** gigetoo has joined #rtems 2014-06-30T23:11:31 *** mkhoory has quit IRC (*.net *.split) 2014-06-30T23:11:32 *** b47378 has quit IRC (*.net *.split) 2014-06-30T23:11:33 *** verm__ has quit IRC (*.net *.split) 2014-06-30T23:11:35 *** ysionneau has quit IRC (*.net *.split) 2014-06-30T23:11:38 *** bmatt has quit IRC (*.net *.split) 2014-06-30T23:22:50 *** mkhoory has joined #rtems 2014-06-30T23:22:50 *** b47378 has joined #rtems 2014-06-30T23:22:50 *** verm__ has joined #rtems 2014-06-30T23:22:50 *** ysionneau has joined #rtems 2014-06-30T23:22:50 *** bmatt has joined #rtems 2014-07-01T01:58:45 *** mkhoory has quit IRC (Ping timeout: 244 seconds) 2014-07-01T03:22:19 *** sebhub has joined #rtems 2014-07-01T03:27:06 good morning 2014-07-01T06:44:15 good morning sebhub 2014-07-01T07:17:16 *** atgreen has joined #rtems 2014-07-01T07:34:13 *** phipse has joined #rtems 2014-07-01T07:34:30 hi 2014-07-01T07:37:34 *** atgreen has quit IRC (Ping timeout: 264 seconds) 2014-07-01T07:38:02 *** asuolen has joined #rtems 2014-07-01T07:44:50 *** atgreen has joined #rtems 2014-07-01T07:44:59 *** Sched has joined #rtems 2014-07-01T07:46:51 *** gedare has joined #rtems 2014-07-01T07:47:42 *** verm__ has quit IRC (Changing host) 2014-07-01T07:47:42 *** verm__ has joined #rtems 2014-07-01T07:47:51 good morning everyone 2014-07-01T07:47:59 Hi 2014-07-01T07:48:38 Hi everyone! 2014-07-01T07:49:52 *** ppisa has joined #rtems 2014-07-01T07:50:40 *** JustJanek has joined #rtems 2014-07-01T07:51:16 *** Hesham has joined #rtems 2014-07-01T07:52:57 https://docs.google.com/document/d/1H0poxrC2KMtQTMEQKH3k0ynSvjEMsLagtYKDxFm16i0/edit?usp=sharing 2014-07-01T07:55:06 hello 2014-07-01T07:55:16 g'day 2014-07-01T07:56:20 Hi 2014-07-01T07:57:23 *** jenniferA has joined #rtems 2014-07-01T07:57:30 *** AoLaD has joined #rtems 2014-07-01T07:59:44 *** DrJoel has joined #rtems 2014-07-01T07:59:44 *** DrJoel has joined #rtems 2014-07-01T07:59:44 *** ChanServ sets mode: +o DrJoel 2014-07-01T08:00:15 https://docs.google.com/document/d/1H0poxrC2KMtQTMEQKH3k0ynSvjEMsLagtYKDxFm16i0/edit?usp=sharing 2014-07-01T08:00:41 You are up early this morning 2014-07-01T08:00:47 i need coffee 2014-07-01T08:00:52 well you are on Eastern time 2014-07-01T08:01:12 ok, let's start.. 2014-07-01T08:01:12 my nephew is visiting and apparently I don't have any computer available which is good enough for his gaming. lol 2014-07-01T08:01:23 asuolen: can you begin? 2014-07-01T08:02:11 sure 2014-07-01T08:03:03 *** krzysiekm13 has joined #rtems 2014-07-01T08:04:32 so this week I have began the work on GPIO interrupts. It seems to be working. I just need to polish some issues 2014-07-01T08:05:01 ok good 2014-07-01T08:05:17 Did you solve the argumetn to the ISR issue? 2014-07-01T08:06:02 as the handler arguments I mentioned yesterday on the mailling list, and button deboucing (i am using a button to test the interrupts, but it is generating more than one interrupt when i release it, i sustect it it the button itself bouncing) 2014-07-01T08:06:33 Yes. The button could bounce a lot based on my experience. 2014-07-01T08:06:33 debouncing is common hw issue 2014-07-01T08:06:46 DrJoel: can I call printk from an ISR? 2014-07-01T08:07:00 A generic debouncing algorithm as a helper method to attach to a pin would be nice. 2014-07-01T08:07:19 Yes. But obviously calling it slows the execution down. It is sometimes useful but keep them short 2014-07-01T08:07:23 " if you set BSP_output_char_function_type BSP_output_char = your_output_char; accordingly" 2014-07-01T08:07:47 Currently I am "reading" the value by using a global variable and printing that. Anyway the values that are getting to the handler are not what they were supposed to 2014-07-01T08:07:49 hmm, on 4.11 it might just be doable 2014-07-01T08:08:17 asuolen: post your code to github and send more detailed explanations of what you've tried 2014-07-01T08:08:27 and the behavior you witness 2014-07-01T08:08:37 please. There are some common things that can cause it. 2014-07-01T08:08:47 ok will do that 2014-07-01T08:09:11 *** Sched has quit IRC (Ping timeout: 248 seconds) 2014-07-01T08:09:32 *** Sched has joined #rtems 2014-07-01T08:09:39 after you get this working, what's next? 2014-07-01T08:09:46 apart from that the GPIO API could use pin grouping IO, but I am focusing on the RPI now and the RPI can live without it for now. When this is done I suppose the GPIO part will be done 2014-07-01T08:10:03 ok good i think you should move on also 2014-07-01T08:10:26 it has dragged on enough after all, you didn't propose RTEMS GPIO :) 2014-07-01T08:11:35 also, for any of you students who are in Europe and can travel to Portugal: http://www.sigops-france.fr/Main/EWiLi14 2014-07-01T08:11:45 well it would be a matter of readjusting the code a bit, and I can propose or show a little proof of concept at least of what I had in mind for it 2014-07-01T08:11:45 you may like to write a small paper about your gsoc :) 2014-07-01T08:12:25 Ha, I'm from Portugal! 2014-07-01T08:12:27 OK... anything else asuolen ? 2014-07-01T08:12:45 gedare: Thanks for sharing this, would any of my projects can make a good paper ? 2014-07-01T08:12:51 we can discuss it offline 2014-07-01T08:13:32 gedare: i guess not 2014-07-01T08:13:35 next up, Sched can you go? hi phipse 2014-07-01T08:13:36 thanks asuolen 2014-07-01T08:13:38 hi 2014-07-01T08:14:09 Ok 2014-07-01T08:14:20 Last Week I got five final examinations, as a result, I have to spent lots of time to prepare it and have little time work with GSoC. 2014-07-01T08:14:35 now you are done with exams? 2014-07-01T08:14:49 Yes 2014-07-01T08:14:56 Now I'm trying to running hello world of RTEMS guest on POK's hypercall and vCPU framework. 2014-07-01T08:15:49 ok, so no change from last week then? 2014-07-01T08:16:26 I'm hampered by some sensitive instructions. It seems the hello world example in POK can't be running again. I must find out the reason and replace it with hypercall and vCPU. 2014-07-01T08:16:37 Ok 2014-07-01T08:17:03 That what I need to do this week. 2014-07-01T08:17:14 sounds good.. anything else? 2014-07-01T08:17:18 to report today 2014-07-01T08:17:33 do you have a guess, where this sensitive instruction comes from? 2014-07-01T08:17:34 After this, I will fill more operation in Hypercall and vCPU. 2014-07-01T08:18:25 How abot a two partition system with two hello worlds as a next step? 2014-07-01T08:18:34 And how far is this from ticker running in a partition? 2014-07-01T08:19:26 No, I have objdump the POK.S and partitions.bin to see where is the reason located. But did not figure out yet. 2014-07-01T08:19:33 Sched: how about some github source updates? 2014-07-01T08:20:40 When I change the RTEMS code to make the Hello world run, I will push some code. 2014-07-01T08:21:10 Sched: you should be pushing code mostly as you write it 2014-07-01T08:21:43 definitely at least every week, preferably every day 2014-07-01T08:22:09 DrJoel, next step should be interrupt handling, and the ticker running as a result of this step. 2014-07-01T08:22:17 ok 2014-07-01T08:22:34 OK, but sometime I find my code should be change... 2014-07-01T08:22:51 that's ok you just push the updated code 2014-07-01T08:23:15 Partitions.bin is just a concationation of all partX/partX.elf files, as far as I remember, so you can objdump the original binaries and reduce a layer of indirection 2014-07-01T08:23:20 OK, If that would not confused other to read my commitment. 2014-07-01T08:24:09 Thanks Sched. 2014-07-01T08:24:13 JustJanek: can you go next? 2014-07-01T08:24:23 The partitions.bin is derived from the RTEMS hello world 2014-07-01T08:24:30 yep, no problem 2014-07-01T08:24:32 Ok. Thank you. 2014-07-01T08:25:03 Last week I have been trying the suggestions I've been getting. I have tried a suggestion from the POK mailing list which was changing up the POK_NEEDS_* defines for arinc653/blackboard but it was without any successful result. I have also checked the default partition mode as (suggested by joel for blackboard call problems) for an arinc653 partition on POK (default as in, I haven't changed the mode and I think the generated code do 2014-07-01T08:25:03 esn't change it) and the mode seems to be 'normal'. I found it odd that the arinc653 partition calls are allowed and the blackboard calls not. With successfully calling an arinc653 partition call on pok the next step I took was trying it with rtems on pok and it compiles fine but i cant get it to work yet. I think it's best to pursue that for next time, trying to get an arinc653 partition call working on pok, might have to ask phili 2014-07-01T08:25:04 pp about the errors ive been getting though. 2014-07-01T08:25:39 sorry, had already written a bit so might be a bit chaotic pasting it into irc chat 2014-07-01T08:26:12 so, what was the problem in the end with the arinc653 calls? 2014-07-01T08:26:21 or was it just the blackboard did not work? 2014-07-01T08:26:25 it's rather that some do and some dont work 2014-07-01T08:26:37 it was both blackboard and buffer so far that i've tested and which failed 2014-07-01T08:26:41 ah.. please follow-up to the pok mailing list about your findings 2014-07-01T08:26:54 they may be interested, and it is good to have a record about it. 2014-07-01T08:27:06 will do 2014-07-01T08:27:35 ok, so you are working on getting the call to work from inside rtems-guest now? 2014-07-01T08:27:35 If your test code is posted, then the Pok community may be able to spot something. It is likely an obvious to them configuration error which they will spot given code 2014-07-01T08:27:56 yes, please do post your test code somewhere. 2014-07-01T08:28:07 Do you have a github repo I am not aware of? 2014-07-01T08:28:21 I think I have posted my example code + example .aadl file 2014-07-01T08:28:45 but it was on the pok mailing list directly 2014-07-01T08:29:42 ok JustJanek. please start to post your code on your github account also 2014-07-01T08:29:57 especially now, we need to start to see the code as you make progress toward the ultimate goals of your project. 2014-07-01T08:30:24 no problem 2014-07-01T08:30:33 ill upload my examples and tests 2014-07-01T08:30:49 this goes for all students really, we expect a lot more progress in the second half since there is less school interference, and you should be more familiar with your projects 2014-07-01T08:30:50 thanks. 2014-07-01T08:31:23 JustJanek: Can you post a link to your github account/repo 2014-07-01T08:31:25 please 2014-07-01T08:31:32 https://github.com/JustJanek?tab=repositories 2014-07-01T08:31:39 it's pointed to from the RTEMS_SOC wiki page 2014-07-01T08:31:44 yeah, that. so far nothing rtems related 2014-07-01T08:32:06 make that your first order of business 2014-07-01T08:32:18 it will make it easier to get help with your problems 2014-07-01T08:33:13 yeah, ill be on it right away after the meeting 2014-07-01T08:33:21 thanks 2014-07-01T08:33:38 thanks 2014-07-01T08:34:08 all right. next up, AoLaD can you go? 2014-07-01T08:34:22 sure 2014-07-01T08:34:41 but i dont know what to say 2014-07-01T08:34:47 *** DrJoel has quit IRC (Quit: There's nothing dirtier then a giant ball of oil) 2014-07-01T08:34:50 Much of my status has been summed by ppisa in yesterday email. I’ve test simple usart communication compiled with -march=armv7-r -mthumb -mbig-endian. That means that I should have some working toolchain. I’ve tried to compile my cloned BSP template. It doesn’t work so I’m cleaning it up right now. I suppose that I’ll have some compilable startup BSP for tms570 in next commit. Hopefully 2014-07-01T08:34:50 today. 2014-07-01T08:34:50 After that I need to get RTEMS running on my board. There will be some work with timers, interrupts and tasks switching, I suppose. 2014-07-01T08:35:17 *** Sched has quit IRC (Read error: Connection reset by peer) 2014-07-01T08:35:27 *** Sched has joined #rtems 2014-07-01T08:35:58 *** DrJoel has joined #rtems 2014-07-01T08:35:58 *** DrJoel has joined #rtems 2014-07-01T08:35:58 *** ChanServ sets mode: +o DrJoel 2014-07-01T08:36:06 ok. did you author the patches for the tools? 2014-07-01T08:36:25 The patch was mine. 2014-07-01T08:36:31 ok thanks ppisa. 2014-07-01T08:36:33 But is is only config changes. 2014-07-01T08:36:44 yeah i know, i just want to make sure to keep track 2014-07-01T08:36:57 Premek has prepared tests in his repo https://github.com/AoLaD/rtems-tms570-utils 2014-07-01T08:37:02 probably sebhub can regenerate it or "sponsor" it for GCC inclusion if you ask him 2014-07-01T08:37:15 yeah i see the tests, this is good 2014-07-01T08:37:45 This is horrible hack to test RTEMS tools without RTEMS. 2014-07-01T08:38:00 ok. AoLaD thanks, the first thing to get working is hello world, which requires a context switch and console code 2014-07-01T08:38:07 heh 2014-07-01T08:38:24 ok 2014-07-01T08:38:31 yes I don't know a good solution, it is a "chicken-and-egg" problem. 2014-07-01T08:38:50 all right. 2014-07-01T08:38:56 any other questions/issues? 2014-07-01T08:39:01 AoLaD: ^ 2014-07-01T08:39:08 krzysiekm13: Can you go next? 2014-07-01T08:39:17 yes, of course :) 2014-07-01T08:39:18 thank you gedare 2014-07-01T08:39:32 May it be one goodies we have nice OpenOCD scripst in the test repo. 2014-07-01T08:39:45 in the last week I have ported pc386 bsp to rtems-test 2014-07-01T08:40:01 That is all from me. 2014-07-01T08:40:14 ppisa: yes some might be interested in this. it could be considered to go toward rtems-test framework. 2014-07-01T08:40:19 I am now able to run tests using rtems-test command, in parallel, with pc386 on couverture-qemu 2014-07-01T08:40:33 ppisa: AoLaD: please make sure to separate who wrote what code, for the correct authorship and final submission of code samples to Google. Thanks. 2014-07-01T08:40:48 krzysiekm13: great work 2014-07-01T08:41:06 it goes well and I am going to polish it and send a patch to rtems-devel list 2014-07-01T08:41:15 krzysiekm13: where do you have your code at? 2014-07-01T08:41:20 ok good 2014-07-01T08:41:35 I am not sure how should I share qemu-support - boot hd image 2014-07-01T08:41:45 for SOCIS students I think there is less strict requirement to have the code always available, but it is best to have a github with your work-in-progress anyways 2014-07-01T08:41:51 hmmm... 2014-07-01T08:42:17 if it is not that big, a binary blob in the repo might not be too bad... 2014-07-01T08:42:22 you should ask kiwichris. 2014-07-01T08:42:25 and where should it be putted, but i will send mail to chris, maybe he will have some advice 2014-07-01T08:42:38 Yeah. 2014-07-01T08:43:17 yes, this is quite small - i will check how small it can be :) 2014-07-01T08:43:18 AoLaD: ppisa: please add license info to the tms570-utils files or repo as a whole, thanks 2014-07-01T08:43:29 heh, ok 2014-07-01T08:43:39 so you will clean it up, then what? 2014-07-01T08:43:55 now, I started to refactor do_coverage script to familiarize myself with existing code and to reorganize coverage reporting 2014-07-01T08:44:29 so I should have it done in next days, and than I will start migrate it to python as coverage module within rtems-test 2014-07-01T08:45:23 ok super 2014-07-01T08:45:51 I think that's all for now :-) 2014-07-01T08:46:13 great.. when you need a double check on testing let me know. 2014-07-01T08:46:24 ok. last up is Hesham 2014-07-01T08:46:26 ok, I will 2014-07-01T08:46:31 ok... 2014-07-01T08:46:32 hi Hesham , beng-nl 2014-07-01T08:46:36 *** krzysiekm13 has quit IRC (Quit: Page closed) 2014-07-01T08:46:40 Hi gedare, beng-nl 2014-07-01T08:47:12 Last week, I have written a series of posts on my blog, describing the status of both the toolchain and RTEMS port and some other tutorials how to build the toolchain and the new or1ksim BSP and how to run hello world and ticker on or1ksim simulator. I am working now on enhancing the code with doxygen style comments and implementing an IRQ manager, just after that, I told Chris that I will submit patches to be merged with RTEMS upstream. 2014-07-01T08:48:03 ok. your code is all on your github though right? 2014-07-01T08:48:08 Regarding IRQ manager, I noticed that there are two APIs (for other architectures) at cpukit and BSP directories, I am a little confused where to implement the IRQ manager 2014-07-01T08:48:11 Yeah 2014-07-01T08:48:13 Ok 2014-07-01T08:48:33 IRQ manger now is just some sort of stubs 2014-07-01T08:48:46 I just posted a long email. Need a link to the manual for the architecture's IRQ handling but it sounds like the PowerPC's to me. 2014-07-01T08:48:48 DrJoel sort of addressed this. There are two ways to handle IRQs at the CPU-layer 2014-07-01T08:48:56 DrJoel: made it a little bit clearer 2014-07-01T08:49:04 What we call "simple vectored" and the PIC models 2014-07-01T08:49:14 I think I will go for rtems mode 2014-07-01T08:49:25 PIC model ... 2014-07-01T08:49:31 if openrisc expects to have a PIC attached, you should use that approach 2014-07-01T08:49:33 *** atgreen has quit IRC (Ping timeout: 240 seconds) 2014-07-01T08:50:01 Yes it expects so, but for or1ksim simulator, it does not 2014-07-01T08:50:12 Then the BSP specific code to decode" 2014-07-01T08:50:16 "decode" 2014-07-01T08:50:25 the PIC will be easy to write but the framework will be in place 2014-07-01T08:50:28 ok, even so, i think it would work, just has 1:1 mapping of irq line to irq vector 2014-07-01T08:50:56 I will take PowerPC and Sparc as examples 2014-07-01T08:50:59 i don't have experience with PIC model in RTEMS 2014-07-01T08:51:02 SPARC uses simple vectored. 2014-07-01T08:51:23 But the SPARC IRQ preamble is architecturally similar. 2014-07-01T08:51:24 SPARC do not use PIC model ? 2014-07-01T08:51:47 Nope... Didn't need it until the LEON3 got too many devices for the number of pins on the CPU 2014-07-01T08:52:06 OK, that made the choice of PowerPC easier 2014-07-01T08:53:01 It is complicated in some ways but essentially the same 2014-07-01T08:53:20 The IRQ code will be in assembly and thus tedious to write. So just be careful 2014-07-01T08:53:37 What has happened to the person from OpenCores who we asked to be involved? 2014-07-01T08:53:51 I think it will need much testing 2014-07-01T08:54:22 DrJoel: I think that's the proper time to communicate with him 2014-07-01T08:54:22 i think we lost him along the way, probably did not keep him involved enough somehow. 2014-07-01T08:54:41 I CCed him with all the updates 2014-07-01T08:54:46 ok 2014-07-01T08:55:04 The previous work was much about RTEMS 2014-07-01T08:55:21 Now that we are into IRQ, we need his help. Please ping him. :) 2014-07-01T08:55:41 Sure, I will contact him today 2014-07-01T08:55:41 I also want to get the binutils and newlib patches upstream. I think we have to wait for them on gcc and binutils. 2014-07-01T08:56:05 DrJoel: Yes I was just writing that I will submit binutils patch this week 2014-07-01T08:56:55 ok.. just have to keep nibbling so it doesn't pile up. :) 2014-07-01T08:56:59 After getting IRQ manager ready, I will submit patches for RTEMS 2014-07-01T08:57:43 Does the OpenRISC have an FPU? 2014-07-01T08:57:44 I was just busy with getting hello world and ticker working and make some blog updates 2014-07-01T08:57:51 Yes 2014-07-01T08:57:58 ticker shouldn't work until IRQs work.. 2014-07-01T08:58:00 I am not sure or1ksim supports it 2014-07-01T08:58:25 or did you install the clock interrupt directly into the IRQ table? 2014-07-01T08:58:34 double check that. But if we can't test it, we may have to ignore it. 2014-07-01T08:58:42 I get around this by writing some hard coded handler at the proper _timer address 2014-07-01T08:58:48 But yes it does not work properly 2014-07-01T08:58:57 ah, ok. 2014-07-01T08:59:45 DrJoel: If or1ksim does not support it, I can re-work on FPU when I got to the HW verification using the FPGA board 2014-07-01T09:00:02 does the architecture allow optional FPU? 2014-07-01T09:00:10 Yes 2014-07-01T09:00:38 ok. there is some trickiness involved with that 2014-07-01T09:00:40 The architecture need a control unit implemented for any implementations 2014-07-01T09:00:48 All other features are optional 2014-07-01T09:00:54 ok sure 2014-07-01T09:01:11 Another thing... 2014-07-01T09:01:18 My graduation project seminar would be next Saturday or Sunday, so I was a little bit busy preparing for it. 2014-07-01T09:01:33 That is to be expected. 2014-07-01T09:01:47 OK 2014-07-01T09:01:58 But, I have already done most of hard work related to preparations 2014-07-01T09:02:18 If you have things whichi require feedback from others, do them so they can work on the feedback while you finish up your preparation. 2014-07-01T09:02:38 that's it for the meeting today, please update the document: https://docs.google.com/document/d/1H0poxrC2KMtQTMEQKH3k0ynSvjEMsLagtYKDxFm16i0/edit 2014-07-01T09:02:50 Just as in CPU architectures, you can fill the delay slot with useful work. :) 2014-07-01T09:03:03 DrJoel: That's why I posted about ISR to the mailing list 2014-07-01T09:03:12 :) 2014-07-01T09:03:12 gedare: I will just after the meeting 2014-07-01T09:03:24 Thanks everyone! 2014-07-01T09:03:30 Congrats on passing the midterms! 2014-07-01T09:03:32 DrJoel: They have two implementations 2014-07-01T09:03:33 :) 2014-07-01T09:03:43 gedare: Thanks :) 2014-07-01T09:03:59 OpenRISC has recently added no-delay slot implementation 2014-07-01T09:04:37 FWIW delay slots are pains when writing assembly. :) 2014-07-01T09:04:58 Some of the IRQ code is even aware of ld delays and tries to do useful work while the information is being fetched 2014-07-01T09:04:58 I filled it with nops 2014-07-01T09:05:09 I made it useful on setjmp.S 2014-07-01T09:05:23 nah, you just always put a nop ;) 2014-07-01T09:05:45 gedare: Did you see the latest setjmp.S file ? ;) 2014-07-01T09:05:51 no 2014-07-01T09:06:09 looking now 2014-07-01T09:06:44 you should add license and authorship 2014-07-01T09:07:06 I remember I used a delay slot there, but not sure where it is :) 2014-07-01T09:07:27 Aha, I did not care about licence headers yet 2014-07-01T09:07:44 What's the proper one for newlib ? 2014-07-01T09:07:58 bsd 2014-07-01T09:08:14 2-clause bsd is easiest to submit to just about anywhere 2014-07-01T09:08:28 2 paragraph version without advertising. There should be plenty of examples in the COPYING files at the top of the tree 2014-07-01T09:08:59 i think the default is a 3-clause that says you can't use red hat to promote any products ;) 2014-07-01T09:09:00 I will check that 2014-07-01T09:09:26 gtg bye everyone 2014-07-01T09:09:27 I think we do not 2014-07-01T09:09:41 Thanks gedare 2014-07-01T09:09:55 oh, Hesham about whether any of you work is good for a paper to ewili.. 2014-07-01T09:10:29 i'm not sure we ever got quite far enough with the mmu framework 2014-07-01T09:11:13 but that might be of interest there 2014-07-01T09:11:24 It's ok, I will work on MMU for OpenRISC too 2014-07-01T09:11:26 yeah 2014-07-01T09:11:33 better to focus on your coding work 2014-07-01T09:11:40 all right. bye 2014-07-01T09:11:44 Bye 2014-07-01T09:11:47 *** gedare has quit IRC (Quit: Leaving) 2014-07-01T09:11:52 bye 2014-07-01T09:11:56 *** DrJoel has quit IRC (Quit: Clap on! , Clap off! Clap@#&$NO CARRIER) 2014-07-01T09:12:38 *** jenniferA has quit IRC (Quit: Leaving) 2014-07-01T09:13:06 bye 2014-07-01T09:13:23 *** phipse has quit IRC (Quit: leaving) 2014-07-01T09:14:33 *** asuolen has quit IRC (Quit: Lost terminal) 2014-07-01T09:36:25 *** ppisa has left #rtems ("Kopete 0.12.7 : http://kopete.kde.org") 2014-07-01T09:40:07 *** Hesham has quit IRC (Ping timeout: 272 seconds) 2014-07-01T09:59:47 *** Sched has quit IRC () 2014-07-01T10:37:29 *** sebhub has quit IRC (Remote host closed the connection) 2014-07-01T11:12:06 *** JustJanek has quit IRC (Quit: Leaving) 2014-07-01T11:36:35 *** Hesham has joined #rtems 2014-07-01T14:59:25 *** mwalle has quit IRC (Quit: WeeChat 0.3.8) 2014-07-01T15:12:39 *** Hesham has quit IRC (Ping timeout: 248 seconds) 2014-07-01T17:26:56 *** Hesham has joined #rtems 2014-07-01T18:03:30 *** AoLaD has quit IRC () 2014-07-01T18:12:09 *** Hesham has quit IRC (Ping timeout: 244 seconds) 2014-07-01T19:07:44 *** mkhoory has joined #rtems 2014-07-01T19:34:23 *** Hesham has joined #rtems 2014-07-01T19:46:53 *** Hesham1 has joined #rtems 2014-07-01T19:47:38 *** Hesham has quit IRC (Ping timeout: 252 seconds) 2014-07-01T20:11:33 *** Hesham1 has quit IRC (Ping timeout: 272 seconds) 2014-07-01T20:40:16 *** dr__house has joined #rtems 2014-07-01T20:40:16 *** dr__house has joined #rtems 2014-07-01T20:40:46 *** dr__house has left #rtems 2014-07-02T01:04:48 *** sebhub has joined #rtems 2014-07-02T01:05:01 good morning 2014-07-02T02:00:18 *** mkhoory has quit IRC (Ping timeout: 255 seconds) 2014-07-02T02:30:02 *** zoso has joined #rtems 2014-07-02T04:16:22 *** gigetoo has quit IRC (Remote host closed the connection) 2014-07-02T04:18:24 *** gigetoo has joined #rtems 2014-07-02T07:20:30 *** Hesham has joined #rtems 2014-07-02T08:39:24 *** cdesai has joined #rtems 2014-07-02T09:09:06 good morning sebhub 2014-07-02T09:11:17 *** sebhub has quit IRC (Remote host closed the connection) 2014-07-02T09:27:06 *** zoso has quit IRC (Remote host closed the connection) 2014-07-02T09:40:30 *** atgreen has joined #rtems 2014-07-02T09:50:10 *** atgreen has quit IRC (Ping timeout: 264 seconds) 2014-07-02T09:51:03 *** Hesham has quit IRC (Ping timeout: 248 seconds) 2014-07-02T11:07:16 *** Hesham has joined #rtems 2014-07-02T12:33:13 *** Hesham has quit IRC (Ping timeout: 272 seconds) 2014-07-02T12:44:59 *** monstr has joined #rtems 2014-07-02T13:58:34 *** monstr has quit IRC (Ping timeout: 264 seconds) 2014-07-02T15:23:09 *** Hesham has joined #rtems 2014-07-02T16:21:59 *** Hesham1 has joined #rtems 2014-07-02T16:23:03 *** Hesham has quit IRC (Ping timeout: 240 seconds) 2014-07-02T19:06:32 *** mkhoory has joined #rtems 2014-07-02T23:07:01 *** atgreen has joined #rtems 2014-07-03T00:21:22 *** atgreen has quit IRC (Ping timeout: 264 seconds) 2014-07-03T00:43:21 *** sebhub has joined #rtems 2014-07-03T01:15:33 good morning 2014-07-03T01:35:03 *** Hesham1 has quit IRC (Ping timeout: 248 seconds) 2014-07-03T02:01:08 *** zoso has joined #rtems 2014-07-03T02:01:59 *** zoso has joined #rtems 2014-07-03T02:01:59 *** mkhoory has quit IRC (Ping timeout: 272 seconds) 2014-07-03T02:02:44 *** zoso