02:22 | aombk | left the channel | |
02:22 | aombk | joined the channel | |
02:45 | futarisIRCcloud | left the channel | |
02:56 | mumptai_ | joined the channel | |
03:00 | mumptai | left the channel | |
04:32 | Bertl | off to bed now ... have a good one everyone!
| |
04:32 | Bertl | changed nick to: Bertl_zZ
| |
04:58 | lexano | joined the channel | |
05:16 | megora | joined the channel | |
05:16 | megora | left the channel | |
06:57 | BAndiT1983|away | changed nick to: BAndiT1983
| |
08:41 | mumptai_ | left the channel | |
08:41 | mumptai | joined the channel | |
13:08 | futarisIRCcloud | joined the channel | |
13:16 | Bertl_zZ | changed nick to: Bertl
| |
13:16 | Bertl | morning folks!
| |
13:19 | BAndiT1983 | hi
| |
13:31 | schmoggie | left the channel | |
15:15 | se6ast1an | good day
| |
15:50 | Aditya | joined the channel | |
15:52 | se6ast1an | hi Aditya!
| |
15:52 | se6ast1an | welcome to our IRC channel!
| |
15:55 | Aditya | Hi
| |
15:56 | Aditya | Thanks
| |
15:57 | se6ast1an | is it ok if I paste what you wrote in your email here for those who did not yet read it ?
| |
15:57 | Aditya | sure
| |
15:58 | se6ast1an | I am Aditya Bansal, a second-year bachelors in Design student at Delhi Technological University where my specialization includes Interaction Design, Brand Strategy and cognitive ergonomics. I am looking for internship opportunities to work as part of your design team or contribute to a project. I understand due to COVID-19 Pandemic these are tough situations from both corporations and applicants, any opportunity is welcomed.
| |
15:58 | se6ast1an | My experience includes working as a project intern at Defense Research and Development Organisation, I have also interned as UI/UX designer for Skilling You and EasyPG, helping them create meaning user interfaces for their digital services. I have undertaken various projects from evaluating Cognitive behavior of individuals to developing complete corporate identity of cloud gaming company "Aurora". I have undertaken various certifications from reputed
| |
15:58 | se6ast1an | institutes around the globe on Development and UX design. I have been a global finalist at Hack COVID-19 event. Had multiple publications in the field of Human-computer Interaction.
| |
15:58 | se6ast1an | If you have any requirement for a Design Intern both in office or work from home, do reach me out!
| |
15:58 | se6ast1an | thanks
| |
15:58 | se6ast1an | (updated resume attached)
| |
15:58 | se6ast1an | https://www.behance.net/aditban
| |
15:58 | se6ast1an | https://www.adityaban.com/
| |
16:00 | se6ast1an | before we dive into the matter itself
| |
16:00 | Aditya | yaa
| |
16:00 | se6ast1an | you are looking for an "online internship", kind of like a GSoC student right?
| |
16:01 | Aditya | Yup, kind of that only
| |
16:02 | se6ast1an | great
| |
16:03 | se6ast1an | did you explore our website/wiki a bit already and looked at the things we are working on currently?
| |
16:05 | Aditya68 | joined the channel | |
16:05 | Aditya | left the channel | |
16:05 | Aditya68 | so sorry, there seems to be some issues at my end
| |
16:06 | Aditya68 | could you please repeat after my last message
| |
16:06 | se6ast1an | sure
| |
16:06 | se6ast1an | <Aditya> Yup, kind of that only
| |
16:06 | se6ast1an | <se6ast1an> great
| |
16:06 | se6ast1an | <se6ast1an> did you explore our website/wiki a bit already and looked at the things we are working on currently?
| |
16:06 | se6ast1an | --> Aditya68 (0126f450@1.38.244.80) has joined #apertus
| |
16:07 | se6ast1an | http://irc.apertus.org/index.php?day=18&month=05&year=2020#40
| |
16:07 | Aditya68 | yaa, I looked at the website
| |
16:07 | Aditya68 | To get an idea of what apertus does
| |
16:08 | se6ast1an | great, so do you have any ideas or areas you would like to get involved in already?
| |
16:09 | Aditya68 | I'm more into User research that goes onto building a great user experience of interactions, I'm a design student. Anything that involves a redesign or any research required for that
| |
16:10 | Aditya68 | I'll do
| |
16:10 | Aditya68 | It could be related to designing a better experience of software
| |
16:12 | Aditya68 | It could be related to software of axiom camera
| |
16:12 | Aditya68 | or anything where you think you require help
| |
16:13 | se6ast1an | ok, I have two projects in mind:
| |
16:13 | se6ast1an | The AXIOM Remote: https://wiki.apertus.org/index.php/AXIOM_Remote
| |
16:13 | se6ast1an | The GUI in particular: https://github.com/apertus-open-source-cinema/AXIOM-Remote
| |
16:14 | illwieckz | left the channel | |
16:14 | se6ast1an | and the second project: the AXIOM WebUI
| |
16:14 | se6ast1an | https://files.niemo.de/Screenshot_2019-12-09%20AXIOM-web.png
| |
16:14 | se6ast1an | https://files.niemo.de/Screenshot_2019-12-16%20AXIOM-web%281%29.png
| |
16:14 | se6ast1an | https://files.niemo.de/Screenshot_2019-12-16%20AXIOM-web.png
| |
16:15 | Aditya68 | okay, cool
| |
16:15 | Aditya68 | I think
| |
16:15 | se6ast1an | both are a bit of a challenge to work on remotely without the hardware but there are some ways how that could be solved (will require some effort on your side though
| |
16:15 | se6ast1an | )
| |
16:16 | Aditya68 | yaa I agree but that's okay
| |
16:16 | Aditya68 | I'm comfortable with both of them
| |
16:17 | Aditya68 | Could start with webUI
| |
16:17 | se6ast1an | can you explain a bit how you would like to work or what you would like to do?
| |
16:17 | se6ast1an | what your methods are
| |
16:17 | Aditya68 | certainly
| |
16:19 | illwieckz | joined the channel | |
16:20 | Aditya68 | At first I would start by studying the current UI, it's goal and functions then will analyse the target audience and how current Ui serving to them. Then will conduct Research on what could be more optimal, like finding better ico design and button placement for more reach or what color at what places are required or what should be the navigation
| |
16:20 | Aditya68 | process considering cognitive capabilities of our brain
| |
16:20 | Aditya68 | Some other similar things, based on which I could present a ideation of redesigns
| |
16:21 | Aditya68 | Once finalized, could start implementing them
| |
16:25 | se6ast1an | so you would write an analysis report and create concept art for improvements/redesigns?
| |
16:28 | Aditya68 | yaa that pretty much sums it up
| |
16:29 | se6ast1an | sounds good
| |
16:29 | se6ast1an | I guess we could give it a try if you are up for it
| |
16:30 | se6ast1an | keep in mind that the software and GUI is very much work in progress
| |
16:30 | Aditya68 | thanks, sure
| |
16:30 | Aditya68 | yes
| |
16:30 | se6ast1an | how would you suggest we organize this best?
| |
16:30 | se6ast1an | to keep everyone in the loop
| |
16:31 | se6ast1an | we have weekly IRC meetings on mondays
| |
16:31 | se6ast1an | next one starts in 30 minutes
| |
16:31 | se6ast1an | that could be one way to report about progress weekly
| |
16:31 | Aditya68 | Cool I could present what I did in that meetings
| |
16:31 | se6ast1an | yes
| |
16:31 | Aditya68 | We could have discussion on same
| |
16:31 | Aditya68 | And proceed accordingly
| |
16:32 | se6ast1an | another idea (maybe in addition) would be to maintain/fill/extend a wiki page about your project:https://wiki.apertus.org/index.php/Main_Page
| |
16:33 | Aditya68 | That sounds good as well
| |
16:33 | Aditya68 | I could update what I did there
| |
16:34 | se6ast1an | great, to get stated vup proposed to add some information to the nctrl Readme on github and in combination with the webui readme on github that should serve as a starting point
| |
16:34 | Aditya68 | okay
| |
16:34 | se6ast1an | you will need to install/setup some software to get the webUI operational
| |
16:34 | se6ast1an | nodejs + yarn for the webui, rust for nctrl
| |
16:34 | Aditya68 | Cool
| |
16:35 | se6ast1an | you will need a linux operating system for that
| |
16:35 | Aditya68 | Yaa
| |
16:35 | Aditya68 | I'll have that
| |
16:35 | se6ast1an | your CV does not mention any linux experience yet
| |
16:36 | se6ast1an | do you feel confident? :)
| |
16:36 | se6ast1an | what is your main operating system currently?
| |
16:36 | Aditya68 | Yup it would be a challenge
| |
16:36 | Aditya68 | Currently I operate on windows
| |
16:36 | se6ast1an | as a virtuaization might be more straight forward (virtualbox for example)
| |
16:38 | Aditya68 | yaa
| |
16:38 | Aditya68 | that's true
| |
16:38 | se6ast1an | so this might be a good starting point: https://www.youtube.com/watch?v=hvkJv71PsCs
| |
16:38 | Aditya68 | cool, thanks for that
| |
16:38 | Aditya68 | I'll do the same
| |
16:39 | se6ast1an | anyway, whenever you have a question or need help/support come here and ask
| |
16:39 | Aditya68 | sure, I'll do necessary basic work
| |
16:39 | se6ast1an | we do expect some independence though
| |
16:39 | Aditya68 | and then will report back
| |
16:39 | Aditya68 | thanks for that
| |
16:39 | se6ast1an | aka we cannot explain ever button click to you
| |
16:39 | vup | ok, I added some basic instructions for the control daemon here: https://github.com/apertus-open-source-cinema/nctrl/blob/master/Readme.md#getting-started
| |
16:40 | se6ast1an | great, thanks vup
| |
16:40 | vup | which works together with these here: https://github.com/apertus-open-source-cinema/webui#develop
| |
16:40 | se6ast1an | Aditya68: please create an account on our wiki
| |
16:40 | Aditya68 | sure,will do that
| |
16:41 | se6ast1an | and feel free to stick around to the IRC meeting in 20 minutes
| |
16:41 | vup | Aditya68: if you run into problems feel free to ping me, even if I don't respond immediately I will be reading the IRC log and answer when I come back. You should probably also read the log (http://irc.apertus.org/) to avoid missing any responses in case your IRC client cuts out
| |
16:42 | se6ast1an | note the public meeting logs
| |
16:42 | se6ast1an | http://irc.apertus.org/
| |
16:42 | Aditya68 | thanks
| |
16:42 | Aditya68 | will take note of it
| |
16:42 | se6ast1an | you can read up on last weeks meeting for example
| |
16:42 | se6ast1an | last monday: http://irc.apertus.org/index.php?day=11&month=05&year=2020#132
| |
16:44 | Aditya68 | yaa, that would be great
| |
16:47 | Aditya68 | left the channel | |
16:48 | megora | joined the channel | |
17:00 | se6ast1an | MEETING TIME!
| |
17:00 | se6ast1an | welcome everyone!
| |
17:00 | se6ast1an | please direct message me now if you want to report and I will put everyone into order
| |
17:01 | se6ast1an | bluez_[m]: please get this start :)
| |
17:01 | se6ast1an | *started
| |
17:01 | preetimenghwani[ | * preetimenghwani is here
| |
17:02 | bluez_[m] | thanks sebastian!
| |
17:02 | bluez_[m] | hello everyone
| |
17:02 | bluez_[m] | so last week i build the kernel for both the betas and set them up (along with vup and bertl)
| |
17:03 | bluez_[m] | we also added a fallback "golden" image (which we can select at boot) in case anything goes wrong with the test kernel
| |
17:04 | se6ast1an | "both the betas" you mean the remote access betas bertl is operating right?
| |
17:04 | bluez_[m] | ah, yes those betas
| |
17:04 | se6ast1an | great!
| |
17:05 | bluez_[m] | i also built and tested some dummy modules and also set up an initial github repo and a simple makefile for my gsoc project
| |
17:06 | bluez_[m] | i could not actually code anything yet though, i realized i had to read a lot of stuff about the i2c subsystem in linux, do did mostly that
| |
17:06 | bluez_[m] | so* did
| |
17:07 | bluez_[m] | but i'll get coding soon... i have everything i need for building and running the kernel driver
| |
17:07 | bluez_[m] | only need some more information
| |
17:07 | bluez_[m] | that's it from my side!
| |
17:07 | se6ast1an | many thanks! any comments/questions for bluez_[m]?
| |
17:08 | se6ast1an | I am sure Bertl will help you with the questions you have or the information you need soon
| |
17:08 | se6ast1an | next uP. metal_dent[m]! - please go ahead
| |
17:09 | metal_dent[m] | alright!
| |
17:09 | bluez_[m] | <se6ast1an "I am sure Bertl will help you wi"> ah, ofc he does... we are also going to discuss something right after the meeting
| |
17:10 | metal_dent[m] | in the last meeting I had reported that i created a makefile for the image conversion which was quite longer so first i shorten it (used wildcards etc)
| |
17:11 | metal_dent[m] | then for image xbm to image header i created a sample header file which has the correct structure and i added a function in makefile which used "sed" to get width, height and pixel data from xbm and replaced "place holders" in the sample headers
| |
17:12 | metal_dent[m] | this is how i tried to create all the image header files which look good (but maybe Bertl wants to improve something ;)
| |
17:12 | Bertl | the comment I wanted to add last time (but forgot to :) is this:
| |
17:13 | Bertl | you might want to make good use of the 'unix pipelining' instead of creating temporary files with fixed names
| |
17:13 | metal_dent[m] | also i worked on the ImageButton to make button size and position variable (with se6ast1an 's help) and also modified the SetButton() method in ButtonBar
| |
17:13 | Bertl | the reason for this is that once you have a bunch of images you want to convert and you run make with parallel building to speed up things, you'll get some strange effects
| |
17:14 | metal_dent[m] | oh okay, will look into that
| |
17:15 | metal_dent[m] | also i connected successfully with the remote-remote and today i flashed firmware and bootloader in that
| |
17:16 | metal_dent[m] | minicom part is left as that requires some additional stuff which we'll discuss after this meeting
| |
17:16 | metal_dent[m] | so that's it from my side :)
| |
17:16 | se6ast1an | great, many thanks
| |
17:17 | se6ast1an | note that commited a breaking build yesterday so if you flash the latest code its expected to not be working right now
| |
17:17 | se6ast1an | I should fix that in the next couple of days
| |
17:17 | Bertl | yes, although I'm not sure whether the firmware was working as intended, so we should double check that :)
| |
17:17 | se6ast1an | or you can just flash a previous commit state
| |
17:18 | se6ast1an | *note that I commited
| |
17:18 | Bertl | it might make sense to have a short test session with BAndiT1983 after the meeting to try a few things
| |
17:18 | metal_dent[m] | noted ;)
| |
17:18 | se6ast1an | great
| |
17:18 | se6ast1an | preetimenghwani[: you are next
| |
17:19 | preetimenghwani[ | <metal_dent[m] "noted ;) "> Thanks se6ast1an
| |
17:20 | preetimenghwani[ | Firstly I tried to understand the current pixel remapper but it was quite tricky, so could only get an overview, then i read about the different types of memory resources available, discussed with bertl about the current remapper and the sequence used by it, also discussed ideas on how things can be improved, read about the zynq architecture(i.e the components of PS and PL), the types of AXI interfaces(stream and
| |
17:20 | preetimenghwani[ | memory mapped, currently understanding the AXI DMA, my next task will be focussing on preparing a rough sketch of how the remapper will be implemented.
| |
17:22 | preetimenghwani[ | Thats it from my side :)
| |
17:24 | se6ast1an | great, many thanks!
| |
17:24 | se6ast1an | BAndiT1983: please share your rich progress
| |
17:24 | BAndiT1983 | hello everyone
| |
17:25 | BAndiT1983 | don't know if rich progress or not, but had to change a bit my field of activity, besides remote firmware and visualiser
| |
17:25 | se6ast1an | definitely rich! :)
| |
17:25 | BAndiT1983 | done some fixes and adjustments for them, but had a plan to finalize the virtual camera preview and serial communication
| |
17:26 | BAndiT1983 | but as we also have other urgent task had to switch to other ones:
| |
17:26 | BAndiT1983 | number 1: for the sony e-mount sniffing we need a possibility to use 3.0V, to prevent damages to the lens and MCU
| |
17:27 | BAndiT1983 | but the problem was that we couldn't find a replacement for the 3.3V voltage regulator on the teensy 3.5, after a couple of discussion it was decided to order teensy 4.0 and suitable 3.0V voltage regulator
| |
17:28 | BAndiT1983 | as i had no suitable tools for replacement, also a heat gun soldering station was ordered, now i'm trying to get comfortable with the usage of it and modify the teensy for schmoggie1
| |
17:28 | BAndiT1983 | if everything works out, then he will receive it this week, as he lives not far from me
| |
17:29 | BAndiT1983 | number 2: had to return to the scene of my previous crime, namely a python script for extracting the positions of elements on a PCB for the PCB probe machine
| |
17:30 | BAndiT1983 | as the parts are exported in the order they were created or whatever sorting EAGLE prefers, the PCB probe would move a lot around, which is not that optimal and requires too much time
| |
17:30 | BAndiT1983 | example images of my attempts are currently here: https://superuser.com/questions/999581/pipe-and-stdin-redirection-to-cat
| |
17:30 | BAndiT1983 | sorry, wrong link: https://lab.apertus.org/T1199
| |
17:31 | BAndiT1983 | after last analysis it was clear that a grouping/clustering of pads is required which are too far apart, but belong to some package which has the origin in the center, this is what i will try to do after soldering adventure
| |
17:31 | BAndiT1983 | that would be it from me
| |
17:32 | se6ast1an | anything to report about the panelzation scripting efforts of PCBs?
| |
17:32 | BAndiT1983 | ah, thanks for reminding
| |
17:33 | BAndiT1983 | this is another python-based development, using pcb-tools and pcb-tools extension, former one for loading Gerber data which was exported from EAGLE, latter one for panelization, the results are rather promising, also using ezdxf to creation additional elements, like special paths or texts
| |
17:34 | BAndiT1983 | when there is a stable version, then both repos, panelizer and pcb-probe extractor should be moved to apertus repo from my own ones
| |
17:34 | se6ast1an | great!
| |
17:34 | se6ast1an | aynthing else BAndiT1983?
| |
17:35 | BAndiT1983 | now that would be it (quite some typos when typing fast ;) )
| |
17:35 | se6ast1an | thanks :D
| |
17:35 | se6ast1an | vup you have some news for us as well!
| |
17:35 | vup | Yep
| |
17:35 | vup | On mobile so bear with me...
| |
17:38 | mumptai | left the channel | |
17:38 | mumptai | joined the channel | |
17:38 | se6ast1an | quick intermission: panintended messageed me he is sorry he currently can't attend as he is in another meeting right now.
| |
17:38 | se6ast1an | From the top of my head he completed the knob button pressing feature in the AXIOM Remote visualizer in the last week and is now working on the button down event registration in the visualizer.
| |
17:39 | vup | I did some more finishing work on the micro r3 schematic, mostly picking out the caps and resistors we want to use (mostly determining their size).
| |
17:39 | vup | Instead of the clock generator mentioned last time (5P49V6965) we decided to go for a simple fixed frequency (100Mhz) crystal oscillator (SG5032VAN) because we don't actually need the flexibility of a clock generator if we just want to usb c.
| |
17:39 | vup | Furthermore anuejn and I worked more on the HDMI gateware and finally got it working (stupid mistake, hsync and vsync were transmitted on the wrong channel...).
| |
17:39 | vup | After that we investigated the camlink 4k further, as it seems like a nice and cheap solution to record footage from the micro and beta until we have our own recorder.
| |
17:39 | vup | Unfortunately currently neither Bertl's HDMI gateware or our HDMI gateware seem to work with it. However comparing the registers of the IT6801 between working and not working video feed, shows some interesting differences that we will investigate further after the axi register rewrite anuejn is working on is done and working (building a bitstream for every small change is not fun).
| |
17:39 | vup | I also hopefully fixed most of the bringup-scripts on the new firmware, so Bertl can finally also use the new firmware.
| |
17:39 | vup | Ok
| |
17:40 | vup | Apart from any questions that would be it
| |
17:40 | se6ast1an | great! what are the current camlink issues with the signal?
| |
17:40 | Bertl | I'll get to that when I report
| |
17:40 | se6ast1an | great!
| |
17:40 | se6ast1an | thanks vup!
| |
17:41 | se6ast1an | quick update from me:
| |
17:41 | se6ast1an | from my side it was mostly AXIOM Remote GUI progress: a new numeric selection dialog (with parameters: minimum, maximum, step size and suffix), example video: https://lab.apertus.org/T1177#17130
| |
17:41 | se6ast1an | Now I am working on implementing the so called "observer design pattern" (thanks Bandit): https://refactoring.guru/design-patterns/observer/cpp/example so that there is a central database (object) holding all the camera/remote relevant parameters in the remote and values. Other objects like dialogs or menu items can subscribe to said central database values and get updated (notified) when a value changes or any other action is to be taken.
| |
17:42 | se6ast1an | as the raw image conversion/development progresses with maxime and bertrand in brussels I would like to create an article/guide/tutorial
| |
17:42 | se6ast1an | summarizing our lessons learned
| |
17:42 | se6ast1an | but I am not sure who and when exactly...
| |
17:43 | se6ast1an | would be handy for me to have a working beta with me, maybe Bertl can help on that front soon
| |
17:43 | se6ast1an | thats it from my side
| |
17:43 | se6ast1an | Bertl: your turn!
| |
17:43 | Bertl | okay, so I've spent most of the time adjusting the GSoC remote setup
| |
17:44 | Bertl | and testing various things both GSoC related and otherwise
| |
17:44 | Bertl | we decided to add to the current setup with two remotes (v0.9 and v0.14 one)
| |
17:44 | Bertl | and the two partial betas
| |
17:45 | Bertl | the current setup now also has an RPi which basically functions as signal generator
| |
17:45 | Bertl | and two CamLink4K modules, one connected to the RPi and the other to the second beta via HDMI plugin
| |
17:46 | Bertl | this allows us to generate test images on the RPi and capture them via the CamLink4K
| |
17:46 | Bertl | and we hoped to do the same with the HDMI feed generated from the Beta, but so far no luck
| |
17:47 | Bertl | we extended the scripts to interact with the CamLink4K to be able to dump the register settings on the IT6801 (the HDMI receiver)
| |
17:47 | Bertl | so we can basically take a look at what the CamLink4K is 'seeing'
| |
17:47 | Bertl | and currently it looks like the receiver is not able to process the signal properly
| |
17:48 | Bertl | another addition to the remote setup is the SD remote which is connected via a special I/O shield to the second beta
| |
17:49 | Bertl | and the remote control shield for the Axiom Remote on the first beta
| |
17:49 | Bertl | there we have some unexpected issues, as the Remote seems to be stuck in reset
| |
17:50 | Bertl | this is something I plan to investigate and test in the next few days
| |
17:50 | Bertl | all the bits and pieces in the remote setup can be remotely controlled so there should be no problem when I'm asleep or away
| |
17:51 | se6ast1an | is the remote setup documented somewhere already?
| |
17:51 | Bertl | not really, but I would suggest to wait another week for that so that we have a stable state :)
| |
17:52 | se6ast1an | right, would make sense to update/replace this wiki page then: https://wiki.apertus.org/index.php/AXIOM_Beta_Remote_Access
| |
17:52 | Bertl | I also did some testing on the ultra-96 USB side
| |
17:52 | se6ast1an | as this setup is likely to stay in your reach and not move to the office anytime soon
| |
17:52 | Bertl | yes
| |
17:52 | Bertl | and the results are both promising and disappointing
| |
17:53 | Bertl | we got the Transcend JetFlash 910 USB sticks for testing usb memory
| |
17:53 | Bertl | they are labeled as 'Read up to 420MB/s' and 'Write up to 400MB/s'
| |
17:54 | Bertl | but not even with high end PC and super duper 3.2 USB controller I can get more than 90MB/s sustained write out of them
| |
17:54 | se6ast1an | well it says "up to" :P
| |
17:55 | se6ast1an | we should probably return them...
| |
17:55 | Bertl | so no idea under what condition thos are supposed to reach 400MB/s, probably only if you do not write anything
| |
17:55 | Bertl | I did some test with the USB-SATA interface as well
| |
17:57 | Bertl | and the results there are not great either, but that is probably due to the SSDs I'm currently using, which are supposed to do 450MB/s sustained write but only achieve about 80MB/s on the ultra-96
| |
17:57 | Bertl | (haven't tested why that's the case yet, but will know more soon)
| |
17:58 | Bertl | the good news is that an USB read over USB-SATA achieves 2x 200MB/s so a total of 400MB/s which is the real world maximum of the USB bus
| |
17:59 | Bertl | so the bus performance seems to be fine, we just need to find the proper device to attach to
| |
18:00 | Bertl | I also extended some of the bringup scripts to work with the new hardware
| |
18:00 | Bertl | and we are currently trying to make the new firmware suitable for bringup as vup already reported
| |
18:01 | Bertl | I guess that's it from my side ...
| |
18:01 | se6ast1an | great progress
| |
18:01 | se6ast1an | many thanks
| |
18:02 | se6ast1an | if there is nobody else with topics/reports that means MEETING CONCLUDED
| |
18:02 | se6ast1an | many thanks everyone for attending!
| |
18:02 | se6ast1an | and pushing this project forward!
| |
18:57 | lexano | left the channel | |
18:59 | lexano | joined the channel | |
19:01 | BAndiT1983 | changed nick to: BAndiT1983|away
| |
19:01 | BAndiT1983|away | changed nick to: BAndiT1983
| |
19:18 | megora | left the channel | |
21:43 | se6ast1an | heading off to bed
| |
21:43 | se6ast1an | good night
| |
22:46 | BAndiT1983 | changed nick to: BAndiT1983|away
| |
22:47 | mumptai | left the channel | |
22:59 | Spirit532 | left the channel | |
23:00 | Spirit532 | joined the channel |