02:03 | tpw_rules | left the channel | |
03:26 | tpw_rules | joined the channel | |
03:43 | Bertl_zZ | changed nick to: Bertl_oO
| |
05:18 | metaldent | joined the channel | |
08:29 | se6astian | good day
| |
15:55 | se6astian | Meeting in 5 minutes
| 15:56 | eppisai | is here!
|
15:57 | tpw_rules | hello
| |
16:00 | se6astian | MEETING TIME
| |
16:00 | se6astian | hello everyone
| |
16:00 | tpw_rules | good morning
| |
16:00 | se6astian | please direct message me now if you have something to report/share
| |
16:01 | se6astian | I will put everyone into order and give everyone a slot to report
| |
16:01 | se6astian | bertl normally goes last but notified me that he is occupied with an emergency tech support issue
| |
16:01 | se6astian | but he wrote me a few lines that I can share with you about his progress
| |
16:02 | se6astian | tpw_rules: please go ahead with your report
| |
16:02 | tpw_rules | alright, hello. i spent some time last week looking through the naps code and preparing a plan to work.
| |
16:03 | tpw_rules | i have a plan for setting up the beta hardware pin definitions in naps, but i am waiting on bertl to finish the sensors so i can test everything. i also have a plan to add the SPI support needed to communicate with the sensor
| |
16:03 | tpw_rules | but i am not sure how i will go about submitting the finished code
| |
16:04 | tpw_rules | that covers what i have on my GSoC timeline for this week. i think that is all from me
| |
16:05 | se6astian | many thanks, about submitting finished code we might also be able to discuss, what are your concerns?
| |
16:05 | se6astian | traditionally everything goes into a github repo
| |
16:05 | tpw_rules | i am just not sure the best way to do it. submit a PR from my own repo? where does design and code review fit?
| |
16:05 | tpw_rules | s/the best/the established/
| 16:06 | anuejn | is here
|
16:06 | se6astian | yes, commit to personal repo, create branches per work packages or features and the create pull requests to merge into main
| |
16:06 | se6astian | code review/feedback happens in the PR
| |
16:06 | tpw_rules | okay!
| |
16:07 | se6astian | vnksnkr: you are next!
| |
16:07 | vnksnkr | Thanks
| |
16:07 | anuejn | also I would be happy if you opened prs early (even if they are not ready yet) so that we have a plattform to discuss stuff
| |
16:07 | vnksnkr | So I've been working on sending signals for the push button
| |
16:07 | vnksnkr | There initially seemed to be some issue with the bounce that were being generated
| |
16:08 | vnksnkr | but it's resolved now
| |
16:09 | vnksnkr | Bertl suggested me to modify the code into a generic 'bounce' entity that can take in any type of input and generate output with bounces
| |
16:10 | vnksnkr | I've been able to do that too..now I need to write a wrapper to channel the signals to the different gpios
| |
16:10 | vnksnkr | https://github.com/vnksnkr/remote-test-system
| |
16:10 | vnksnkr | this is my current progress.. it might need some formatting and tidying up
| |
16:10 | vnksnkr | that's it from me :)
| |
16:11 | se6astian | many thanks!
| |
16:11 | se6astian | eppisai: your turn!
| |
16:11 | eppisai | hello!
| |
16:14 | se6astian | eppisai: are you still with us?
| |
16:14 | eppisai | I had my practicals exams last week, so have little progress this week.. i am anaylysing the code for for proper sepration between the firmware and bootloader.. so it becomes hardware agnostic..
| |
16:15 | se6astian | hmm, what do you mean exactly with "sepration between the firmware and bootloader", can you elaborate
| |
16:17 | eppisai | well. there are modules in firmware that are dependent on the bootloader periperals, but refactoring the code can help to design them properly.. like what i understood so far in transition task, we are needing centralDB for transition variables, which in turn needs to be accessed by display driver in LCDdriver..
| |
16:18 | se6astian | I see
| |
16:18 | eppisai | which creates this dependency on hardware driver, that firmware should not be concerned about..
| |
16:19 | eppisai | so, have been trying to comeup with proper solution.. also BAndiT1983 had included bootloader path in makefile properly
| |
16:20 | eppisai | *also BAnduiT1983 had created a task so i had included
| |
16:20 | se6astian | yes, this topic is definitely something to discuss with BAndiT1983 as well
| |
16:20 | se6astian | great, anything else?
| |
16:20 | eppisai | https://github.com/eppisai/AXIOM-Remote/tree/Transition-Task
| |
16:21 | eppisai | yea.. have not tested on remote yet.. but will do asap.. was busy with college stuff.. :(
| |
16:21 | eppisai | thats it i think..
| |
16:21 | se6astian | many thanks!
| |
16:21 | se6astian | anuejn: please go ahead
| |
16:22 | anuejn | I spend some more quality time with naps. I mostly fixed some small issues and made minor improvements here and there (regarding apertus related stuff).
| |
16:22 | anuejn | Additionally I began writing an HDMI receiver core, which might help us to debug our HDMI related problems (on quite low speed since it doesnt use transcievers and ECP5 based hardware from another project).
| |
16:22 | anuejn | Thats it from my side.
| |
16:23 | se6astian | alright, many thanks!
| |
16:23 | se6astian | Bertl_oO: wrote me a few lines of progress that I would like to share with you
| |
16:24 | se6astian | he is midway through testing the tele produced boards
| |
16:24 | se6astian | we had 4 different boards made and 10 of each
| |
16:25 | se6astian | he finished testing all main boards and all power boards
| |
16:25 | se6astian | there are some boards with issues on the connectors
| |
16:25 | se6astian | wont bore you with the details
| |
16:25 | se6astian | the sensors boards and interface boards are still missing
| |
16:25 | se6astian | once all tests are completed we will contact tele
| |
16:26 | se6astian | Bertl_oO expects he will finish this week
| |
16:26 | se6astian | quick reports from me:
| |
16:26 | se6astian | I just finished shooting the next Team Talk episodes with max
| |
16:27 | se6astian | we did it via video conference this time as meeting in person is still tricky
| |
16:27 | se6astian | but since it works really well this way and required effort is greatly reduced we might stick to that method
| |
16:28 | se6astian | max will start editing the next edition asap
| |
16:28 | se6astian | I still need to upload my footage for him
| |
16:28 | se6astian | on another front I have continued digging through the remaining components returned from the production run from tele
| |
16:28 | se6astian | to count them and put everything in lists, etc.
| |
16:29 | se6astian | and on another front which is less apertus related but not entirely unrelated I shot footage for oscars second feature film last week
| |
16:29 | se6astian | oscar who founded the apertus project
| |
16:30 | se6astian | in case you have no idea who oscar is you can read up a bit here: https://www.apertus.org/award :)
| |
16:31 | se6astian | feature film is in the final phase of post production: https://www.imdb.com/title/tt9178176/
| |
16:31 | se6astian | right, thats it from me
| |
16:31 | se6astian | anyone else with updates?
| |
16:32 | se6astian | manav: ?
| |
16:32 | se6astian | bluez: ?
| |
16:32 | se6astian | metaldent: ?
| |
16:35 | se6astian | ok then! many thanks everyone who participated!
| |
16:35 | se6astian | MEETING CONCLUDED
| |
16:35 | se6astian | gsoc meeting now in #apertus-gsoc
| |
18:00 | metaldent | left the channel |