00:56 | Bertl_oO | off to bed now ... have a good one everyone!
| |
00:57 | Bertl_oO | changed nick to: Bertl_zZ
| |
07:30 | danieeel | joined the channel | |
07:34 | danieel | left the channel | |
09:58 | BAndiT1983|away | changed nick to: BAndiT1983
| |
10:06 | Wanderer_99 | joined the channel | |
10:07 | Wanderer_99 | Can we implement the first T871 VHDL challenge using verilog? (VHDL is mentioned in the website)
| |
10:13 | BAndiT1983 | hi Wanderer_99, VHDL is more preferable, as it's the main language for apertus° FPGA development, but Bertl can give you more precise answer
| |
10:14 | BAndiT1983 | his response from 08.03.2017 -> " no problem with that ... note that all our designs so far are in VHDL, but verilog is not a problem per se, you just have to figure out how to make it work in a mixed design"
| |
10:14 | BAndiT1983 | http://irc.apertus.org/index.php?day=08&month=03&year=2017
| |
10:14 | BAndiT1983 | try this google search, if there was later answer from him for the verilog topic -> verilog site:irc.apertus.org
| |
10:15 | BAndiT1983 | 11:24Bertl for the challenge task, which is VHDL, you definitely need to use VHDL
| |
10:15 | BAndiT1983 | http://irc.apertus.org/index.php?day=04&month=03&year=2019
| |
10:15 | omar31 | joined the channel | |
10:22 | Wanderer_99 | BAndiT1983 Thank you, that was helpful
| 10:39 | preetimenghwani[ | sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/BqeoPxNNsgoloAJDScIpChmg >
|
11:04 | berto_bxl | left the channel | |
11:06 | Bertl_zZ | changed nick to: Bertl
| |
11:06 | Bertl | morning folks!
| |
11:07 | BAndiT1983 | hi
| |
11:07 | Bertl | preetimenghwani[: please try to avoid long messages when you are using the matrix interface as they won't be logged properly in the channel log making it harder for others to follow
| |
11:08 | pratyush | joined the channel | |
11:08 | pratyush | Morning :)
| |
11:08 | Bertl | Wanderer_99: in case the information BAndiT1983 dug out for you was not clear: the VHDL challenge, as the name says, requires you to use VHDL :)
| |
11:13 | danieeel | changed nick to: danieel
| |
11:20 | berto_bxl | joined the channel | |
11:43 | pratyush | Bertl : I have done the formatting
| |
11:44 | Bertl | so I should check again?
| |
11:45 | pratyush | Bertl : Apart from that I am really sorry for the pains you took for my code
| |
11:46 | Bertl | line 32 is your first real formatting issue, although I consider the formatting in lines 18-25 'extreme'
| |
11:46 | pratyush | yes please https://github.com/gr8geek/apertus-challenge/blob/master/characterdevice/chardvr.c
| |
11:51 | BAndiT1983 | first line is already an issue
| |
11:51 | BAndiT1983 | chrdev_init() is in my opinion too long for a function
| |
11:57 | pratyush | Bertl : What IDE do professional kernel developers prefer
| |
11:57 | BAndiT1983 | VIM aor emacs
| |
11:57 | BAndiT1983 | *or
| |
11:57 | BAndiT1983 | and Bertl will probably say VI ;)
| |
11:58 | Bertl | doesn't really matter as long as the result adheres to the kernel coding style
| |
11:58 | Bertl | and yes, my IDE of choice is VIM
| |
11:59 | pratyush | I use sublime :)
| |
11:59 | pratyush | Now I shall also use VIM
| |
11:59 | BAndiT1983 | nah, not geek enough
| |
11:59 | BAndiT1983 | are you sure you will learn VIM that quick?
| |
11:59 | BAndiT1983 | it requires some time to get used to it
| |
12:00 | Bertl | I'd say there is enough time ...
| |
12:00 | BAndiT1983 | one should use the editor he/she is comfortable with
| |
12:01 | BAndiT1983 | not because it's "cool", e.g. for me it's easier to use vscode, as i have already my setup there
| |
12:01 | Bertl | how good is it at handling the kernel style?
| |
12:02 | max_bxl | joined the channel | |
12:02 | BAndiT1983 | if i add the right formatting for clang-format or prettier or whichever tool is there, then it would do same stuff like everywhere
| |
12:02 | max_bxl | hello everyone!
| |
12:02 | BAndiT1983 | just a matter of settings
| |
12:02 | BAndiT1983 | hi max_bxl
| |
12:03 | BAndiT1983 | same can be done in sublime, atom.io etc.
| |
12:04 | bluez_[m] | > Now I shall also use VIM
| |
12:04 | bluez_[m] | A word of caution pratyush, once you get comfortable with vim, it will probably stick to you for the rest of you life....for good ;)
| |
12:05 | Bertl | is that bad? :)
| |
12:05 | pratyush | Gvim is a bit better
| |
12:07 | ashok_singh[m] | hello everyone!!!
| |
12:07 | bluez_[m] | @Bertl Thats why i said for good ;)
| |
12:07 | ashok_singh[m] | Bertl: In Firmware ASCII based line protocol is currently envisioned, is this how we will be commanding beta? I discussed this with bandit too but he feels this topic needs discussion with others as there have been many additions in beta.
| |
12:08 | bluez_[m] | > Gvim is a bit better
| |
12:08 | bluez_[m] | Its the same, just graphical....but i personally prefer the vanilla
| |
12:08 | BAndiT1983 | bluez_[m]: just wait until you enter the world of work, companies are rather different on the topic of tools and environment
| |
12:10 | Bertl | if you work at a place where the company dictates what tools you have to use (against your will), it's probably time to consider a change in employment
| |
12:10 | bluez_[m] | BAndiT1983 that could be true... but I guess the thing that really sticks is the vim bindings... you can get those in many ide's these days...
| |
12:10 | BAndiT1983 | don't think so, that i will jump around, third company and the IT dictates it always, windows like always, macbook was just lucky case
| |
12:11 | BAndiT1983 | best thing is when people approach me and ask what makes the noise at my table, they can't imagine that a macbook also has fans (!!) and it can get loud, my impression is, that people do not use macbooks for work properly
| |
12:12 | Bertl | well, all the years of employment, I've never had a company forcing me to use this or that tool or operating system
| |
12:12 | Bertl | (and that was quite some time ago :)
| |
12:12 | Bertl | so it probably depends on what company you pick ...
| |
12:13 | BAndiT1983 | would've liked to take linux PC, but they haven frozen the plans, so next step is win10 or mac (if the will keep the environment)
| |
12:13 | BAndiT1983 | had different companies, always win, starting with XP and now still at 7
| |
12:13 | BAndiT1983 | so i have to know many tools, between linux, windows and mac
| |
12:13 | Bertl | isn't 7 completely obsolete/unsupported by now?
| |
12:14 | BAndiT1983 | yep, but companies can extend the period by paying or finally switching, which takes time when companies have just played the waiting game
| |
12:14 | bluez_[m] | Bdw Bertl , do you have any auto completion or linting setup for vim to do driver development? I used to use YouCompleteMe but it does not recognize the linux headers... i did set a path to the kernel source but no luck :(
| |
12:15 | pratyush | bluez_[m] same here
| |
12:16 | preetimenghwani[ | Bertl: I am really sorry will take care.Could you please verify that you want similar signals in simulation of Serdes.
| |
12:16 | preetimenghwani[ | https://drive.google.com/file/d/1IRcGCabCMuF6Yf6UC6JikYP8wWFLqOxY/view?usp=drivesdk
| |
12:17 | Bertl | bluez_[m]: for kernel development I'm using cscope and ctags
| |
12:17 | pratyush | Fixed the formatting issue
| |
12:18 | pratyush | Shall we proceed for code testing?
| |
12:18 | Bertl | preetimenghwani[: what exactly am I seeing there?
| |
12:19 | Bertl | pratyush: still lots of formatting errors to fix
| |
12:19 | BAndiT1983 | matrix screensaver ;)
| |
12:19 | bluez_[m] | Bertyl: I do use ctags...but not cscope iirc... i did find an article mentioning these two are good for kernel dev.... will set them up then... thanks!!
| |
12:20 | Bertl | pratyush: line 29/30 for example, line 53, etc
| |
12:21 | Bertl | bluez_[m]: cscope is especially helpful if you are navigating the kernel
| |
12:22 | bluez_[m] | Bertl: you mean that ctrl+] thing that jumps to the definition??
| |
12:24 | Bertl | yes, and generating the definitions for that
| |
12:25 | bluez_[m] | > yes, and generating the definitions for that
| |
12:25 | bluez_[m] | Oh then I already have that :)
| |
12:25 | bluez_[m] | But what about linting though? And autocomplete??
| |
12:25 | preetimenghwani[ | Data_in is the input data to the serializer
| |
12:25 | preetimenghwani[ | Data_out the the output data from deseializer. Depth select is used to select
| |
12:25 | preetimenghwani[ | Whether its 8b,10b or 12b SERDES here it is 12b.
| |
12:28 | preetimenghwani[ | Ready signal is assigned '1' when bitslip is adjusted.
| |
12:28 | preetimenghwani[ | Here it is operating at 300Mhz frequency
| |
12:30 | Bertl | okay, looks good, got a testbench for that?
| |
12:30 | Bertl | also, link to the code?
| |
12:31 | Bertl | bluez_[m]: ctags can do autocompletion although I use it seldom
| |
12:31 | Bertl | bluez_[m]: and what do you need linting for? :)
| |
12:32 | preetimenghwani[ | The code needs a bit formatting will send you the link in sometime :)
| |
12:33 | ashok_singh[m] | > Bertl: In Firmware ASCII based line protocol is currently envisioned, is this how we will be commanding beta? I discussed this with bandit too but he feels this topic needs discussion with others as there have been many additions in beta.
| |
12:33 | ashok_singh[m] | Bertl, I think probably my msg has been missed 😅
| |
12:34 | Bertl | ashok_singh[m]: what firmware, what communication?
| |
12:36 | preetimenghwani[ | Bertl: I wanted to ask what is the priority of projects for Apertus?
| |
12:36 | ashok_singh[m] | ahh.. sry for not elaborating.
| |
12:36 | ashok_singh[m] | actually I am taking about subtask where AXIOM Remote firmware needs to control Axiom Beta camera.
| |
12:38 | bluez_[m] | > bluez_: ctags can do autocompletion although I use it seldom
| |
12:38 | bluez_[m] | Ohh...cool...I'll check it out...maybe I have some things to configure
| |
12:39 | Bertl | preetimenghwani[: in general or are you referring to the GSoC 2020 tasks?
| |
12:39 | bluez_[m] | > bluez_: and what do you need linting for? :)
| |
12:39 | bluez_[m] | Just a luxury... no big deal :)
| |
12:39 | Bertl | ashok_singh[m]: ah, yes, well, we haven't decided how the physical layer will look like, so it should be something which can be handled by RS232, USB, ethernet, etc
| |
12:40 | preetimenghwani[ | GSoC 2020 tasks
| |
12:40 | Bertl | ashok_singh[m]: which kind of suggests to go with an ASCII based protocol and simple commands
| |
12:41 | Bertl | ashok_singh[m]: T731, T1130 and T1131 are rather high priority on the FPGA side
| |
12:42 | Bertl | *preetimenghwani
| |
12:42 | pratyush | Bertl : did the fixing
| |
12:42 | pratyush | Bertl : Are there more kernel related task on which we could work on gsoc?
| |
12:44 | ashok_singh[m] | > ashok_singh: ah, yes, well, we haven't decided how the physical layer will look like, so it should be something which can be handled by RS232, USB, ethernet, etc
| |
12:44 | Bertl | pratyush: currently no, but there might be some in the future
| |
12:45 | Bertl | and no, it is not fixed
| |
12:45 | ashok_singh[m] | so is it something which will be implemented bebore gsoc period or is expected to be part of the subtask only?
| |
12:46 | ashok_singh[m] | > ashok_singh: ah, yes, well, we haven't decided how the physical....
| |
12:46 | ashok_singh[m] | srry for this :😅
| |
12:47 | preetimenghwani[ | Bertl Oh thats great!
| |
12:47 | preetimenghwani[ | I read MachXO2 documentation for T731. It would be really helpful if you can explain the task in bit more detail.
| |
12:50 | Wanderer_99 | left the channel | |
12:54 | Bertl | preetimenghwani[: I think I did a few days ago on the IRC channel, please check the logs and see if you can find that
| |
12:55 | Bertl | (note that there should also be a wealth of information in the logs when you search for MachXO2 and/or Routing Fabric
| |
12:55 | BAndiT1983 | preetimenghwani[: see search parameter in the logs today
| |
13:06 | RexOrCine | left the channel | |
13:06 | RavenLyn | joined the channel | |
13:09 | pratyush | Bertl: formatting done :)
| |
13:09 | RavenLyn | left the channel | |
13:12 | pratyush | for linux kernel coding style the maximim line limit it 80 characters
| |
13:16 | pratyush | left the channel | |
13:47 | preetimenghwani[ | Bertl: I found some information related to MachXO2 in your discussion about T729 but sorry i couldn't find details of T731.
| |
14:09 | omar31 | preetimenghwani[: I think you can find useful information here: http://irc.apertus.org/index.php?day=04&month=04&year=2019
| |
14:18 | preetimenghwani[ | omar31: thanks!
| |
16:11 | BAndiT1983 | changed nick to: BAndiT1983|away
| |
16:12 | supragyaraj | joined the channel | |
16:12 | supragyaraj | Hello there!
| |
16:14 | metal_dent[m] | hey supragyaraj !
| |
16:24 | comradekingu | joined the channel | |
16:42 | comradekingu | left the channel | |
16:49 | comradekingu | joined the channel | |
16:50 | ashok_singh[m] | Hello supragyaraj !!!
| |
16:50 | supragyaraj | HI
| |
16:52 | BAndiT1983|away | changed nick to: BAndiT1983
| |
16:53 | supragyaraj | left the channel | |
16:57 | se6ast1an | meeting in 3 minutes
| |
17:01 | se6ast1an | MEETING TIME!
| |
17:01 | se6ast1an | who is present?
| 17:01 | Bertl | is present
|
17:03 | RexOrMatrix[m] | Aye
| |
17:03 | se6ast1an | good good
| |
17:03 | se6ast1an | any news to report rex?
| |
17:04 | RexOrMatrix[m] | Usual promo and image work. Waiting for text.
| 17:05 | metal_dent[m] | > is also present
|
17:05 | se6ast1an | waiting for what text?
| |
17:06 | RexOrMatrix[m] | Power Board Wiki page needs updated.
| |
17:06 | se6ast1an | and who is going to supply this text?
| |
17:07 | RexOrMatrix[m] | .... Well... That's the question.
| |
17:08 | se6ast1an | ok, anything else to share/discuss?
| |
17:09 | RexOrMatrix[m] | That's it from my side. Thanks.
| |
17:09 | se6ast1an | great, thanks
| |
17:09 | se6ast1an | Bertl: you wanna go next?
| |
17:09 | Bertl | sure, why not
| |
17:10 | Bertl | Spent most of the time last week with GSoC related stuff and PCB rework
| |
17:10 | max_bxl | present!
| |
17:11 | Bertl | Got the ABCP PB firmware to a state that it should be useable but still need to populate one of the new boards
| |
17:12 | Bertl | The question which board would be the best choice led me back to the automated PCB probing project we started planning some time ago (with not too much progress)
| |
17:13 | Bertl | So I decided to see what I can do in this regard and adapted a 3D printer for this purpose ... the basic tests look quite promising, precision is sufficient only thing left there is to write the software to do the actual probing based on the board information
| |
17:14 | Bertl | Should have something to show next week in this regard.
| |
17:14 | BAndiT1983 | do you need assistance there?
| |
17:15 | Bertl | Wouldn't hurt, but it is rather specific
| |
17:15 | BAndiT1983 | that's not a problem, you can place tasks in lab for anything you think would accelerate your work
| |
17:16 | Bertl | On the china PCB fabrication side we managed to get a table with the essential data (not everything, but it's progressing) to calculate impedances
| |
17:17 | Bertl | And on the panel front we are currently collecting the panel sizes which are the basis for designing proper panel layouts for our boards
| 17:17 | vup | is present
|
17:17 | Bertl | I also did some long overdue hardware and software maintainance ...
| |
17:18 | Bertl | Guess that's it from my side for this week.
| |
17:19 | se6ast1an | what kind of maintenance ?
| |
17:19 | Bertl | replacing the cooling system on my workstation, checking the Z-Boxes for GSoC/Remote Beta stuff
| |
17:20 | se6ast1an | ah, right
| |
17:20 | se6ast1an | thanks!
| |
17:20 | se6ast1an | max_bxl: anything to report?
| |
17:20 | max_bxl | yep
| |
17:20 | max_bxl | berto_bxl and I
| |
17:21 | max_bxl | installed his Beta in order to continue our weekly meetings despite the lockdown
| |
17:22 | max_bxl | so we keep on working with it "remotely" and we are now doing a small time-lapse that you'll be able to see later in the night !
| |
17:22 | max_bxl | we went through RCN and darkframe calibration with firmware 2.0
| |
17:23 | max_bxl | which leads to make a new wiki page https://wiki.apertus.org/index.php/Factory_Calibration_(firmware_2.0)
| |
17:23 | max_bxl | and find an issue with pypng that is recorded in phabricator
| |
17:23 | max_bxl | https://lab.apertus.org/T1167
| |
17:24 | max_bxl | it's about it
| |
17:24 | se6ast1an | great, thanks!
| |
17:24 | RexOrMatrix[m] | Can we host this time-lapse on the Wiki please?
| |
17:24 | se6ast1an | how do you mean "host", rex?
| |
17:24 | max_bxl | yes, on the Ambrosia page
| |
17:25 | RexOrMatrix[m] | (Link to it from there I mean)
| |
17:25 | se6ast1an | sure
| |
17:25 | max_bxl | will have to find where to store it actually, because it'll be around 4GB
| |
17:25 | Bertl | That's basically nothing :)
| |
17:25 | se6ast1an | max_bxl: are you willing to also link to the stop motion animation from the wikipage?
| |
17:26 | max_bxl | yes and no, since the RCN and darframe caibs weren't done
| |
17:26 | MoniAlvarez | joined the channel | |
17:26 | max_bxl | but I can link them and specify this issue
| |
17:26 | se6ast1an | and I have already set up anextcloud account for you so that would be an option for the storage
| |
17:26 | se6ast1an | or did I?
| |
17:27 | max_bxl | yep
| |
17:27 | se6ast1an | great
| |
17:27 | RexOrMatrix[m] | What I'm concerned about is if it's listed on the Wiki and at some point down the line there's some changes to where it's stored it then becomes a dead link. So, if we store it somewhere secure possibly.
| |
17:27 | max_bxl | hopefully tonight, maybe tomorrow, it'll be available online and linked in the wiki
| |
17:28 | se6ast1an | sounds good
| |
17:28 | se6ast1an | let us know
| |
17:28 | se6ast1an | metal_dent[m]: do you also want to report your progress?
| |
17:28 | max_bxl | RexOrMatrix[m]: I'll put my email address in case the link is dead and people want to access the image, or something like that
| |
17:29 | max_bxl | *imagers
| |
17:29 | max_bxl | *images
| |
17:29 | MoniAlvarez | left the channel | |
17:30 | metal_dent[m] | sure, I've completed my qualification task for gsoc and have submitted the draft proposal on bootloader improvement which BAndiT1983 , Bertl and supragya have reviewed.
| |
17:30 | metal_dent[m] | I'm currently working on the improvements
| |
17:30 | se6ast1an | sounds good!
| |
17:31 | RexOrMatrix[m] | max_bxl Nah, risk is unnecessary. I'll keep an eye on the links there periodically I guess.
| |
17:31 | metal_dent[m] | thank you!
| |
17:32 | Bertl | which is probably a good time to mention that we will do the weekly reports during GSoC, so everybody gets an idea what the current status is
| |
17:32 | Bertl | where potential problems are and what might help to improve the performance of our students
| |
17:33 | metal_dent[m] | of course! like in the weekly meetings or a separate gsoc meeting?
| |
17:33 | BAndiT1983 | this meeting is also a gsoc meeting usually
| |
17:34 | Bertl | we will see how intense the meetings will be ... preferably one meeting if we can handle/coordinate it
| |
17:35 | BAndiT1983 | for statuses it would be enough, separate meetings for detailed discussions
| |
17:36 | metal_dent[m] | alright
| |
17:37 | se6ast1an | vup you also have some progress to report I think
| |
17:37 | vup | yeah, so
| |
17:37 | vup | 1. Finally found a direct hdmi monitor (benq bl2305)
| |
17:37 | vup | tried all of
| |
17:37 | vup | - normal hdmi live feed
| |
17:37 | vup | - mimg with testpattern
| |
17:37 | vup | - dual_hdmi bitstream
| |
17:37 | vup | for the beta and all worked, aswell as the dual_hdmi bitstream for the micro, and that worked glitchfree aswell
| |
17:37 | vup | also tried vivado 2019.2, didn't seem to make a difference (but couldn't try on my original monitor as I am currently not at home)
| |
17:37 | vup | That means we can probably mark the current approach to the lvds pairs to the plugin modules as working and continue using that for revision 3 of the micro (hdmi being untested was one of the big blockers to continuing the work the revision 3)
| |
17:37 | vup | 2. Continued working on improving the control daemon, specifically started working on a test suite to make future changes easier, hopefully the reworked control daemon with a new API should be ready soon and we can start moving more functionality to it (like handling the remote and starting to convert the various init scripts)
| |
17:38 | vup | 3. as anuejn and me are now pretty convinced that hdmi is working on revision 2 of the micro we started working on revision 3
| |
17:39 | vup | I think we have most of the general changes / features pinned down and are now working on fleshing out the details
| |
17:39 | vup | notable features of revision 3 (that are currently planned, they might change in the future) are:
| |
17:39 | vup | swappable image sensors
| |
17:40 | Bertl | hot swapable? *G*
| |
17:41 | vup | a ecp5 as routing fpga, that has 5G transceivers that could (and are planned) to be used to implement usb 3.1 data transfer
| |
17:41 | Bertl | nice
| |
17:42 | Bertl | would it make sense to prototype that as a plugin module?
| |
17:42 | vup | also currently we are planning to make reduced functionality (like no plugin modules) available without the zturn lite (the zynq fpga board) connected, so that the micro can be used like a usb 3 webcam
| |
17:43 | Bertl | (the USB 3.1 part I mean)
| |
17:43 | vup | Bertl: possibly
| |
17:44 | vup | ok thats it from me I think, any questions?
| |
17:44 | se6ast1an | great, thanks
| |
17:44 | se6ast1an | I will document the planned changes on the wiki
| |
17:45 | se6ast1an | https://wiki.apertus.org/index.php/AXIOM_Micro#Features
| |
17:45 | se6ast1an | already done
| |
17:45 | vup | great
| |
17:46 | se6ast1an | ECP5 Plugin module would indeed be very interesting for the Beta as the FTDI FT600 future looks rather bad from what Bertl reported recently
| |
17:46 | Bertl | yep, might also be a good alternative to the planned FX3
| |
17:47 | vup | yeah thought about prototyping the plugin module with the micro, but maybe doing it the other way around is also a good idea :)
| |
17:47 | Bertl | so I would be inclined to design and prototype a plugin for the ECP5 if you take care of the gateware side and testing :)
| |
17:47 | se6ast1an | is there already a demo/open USB3 implementation available on the ECP5 ?
| |
17:48 | vup | yes, we are planning to make use of https://github.com/enjoy-digital/usb3_pipe
| |
17:49 | se6ast1an | great, did you chat about it with _florent_ already?
| |
17:49 | vup | nope
| |
17:49 | vup | but we most certainly will
| |
17:49 | se6ast1an | great
| |
17:49 | se6ast1an | thanks for the update, anything else vup?
| |
17:50 | vup | nope, I think thats it
| |
17:50 | omar31 | left the channel | |
17:50 | se6ast1an | anyone else who wants to report or share something?
| |
17:50 | BAndiT1983 | maybe me, nothing big
| |
17:50 | se6ast1an | pelase go ahead
| |
17:51 | BAndiT1983 | mostly done preparations for gsoc, like straightening out the firmware code and plans for bootloader
| |
17:52 | BAndiT1983 | another idea i've played with, was PCB rendering as previsualisation or photo replacement, for crisp images and still checking out kicad, kicad stepup which is extension for freecad, to load up kicad 3d pcb data and blender, but they all use different formats
| |
17:52 | se6ast1an | did you email simon already about it?
| |
17:53 | BAndiT1983 | so thinking about how to simplify process and be able to replace models of resistors, capacitors etc. with more optimized ones, as available models have too high poly count, maybe because of CAD conversion
| |
17:53 | BAndiT1983 | yes, Rex did, but no response yet, he emailed in fact to 2 email addresses of him
| |
17:53 | BAndiT1983 | am more focussed on firmware at the moment and only reflecting on PCB stuff
| |
17:53 | BAndiT1983 | that'S it
| |
17:56 | se6ast1an | great, thanks
| |
17:56 | se6ast1an | quick updates from me:
| |
17:56 | se6ast1an | Google season of docs goes into its second round soon
| |
17:56 | se6ast1an | https://developers.google.com/season-of-docs
| |
17:56 | se6ast1an | we should consider particiapting
| |
17:56 | BAndiT1983 | have they raised slot number?
| |
17:56 | BAndiT1983 | last time there were only few
| |
17:56 | se6ast1an | I am sure they will accept more orgs this year so we have a good chance to get in hopefully
| |
17:56 | Bertl | I'm in
| |
17:57 | se6ast1an | great, lets discuss it and prepare the application soon then
| |
17:58 | se6ast1an | quick look at the gsoc timeline
| |
17:58 | se6ast1an | official applications opened last week
| |
17:58 | se6ast1an | deadline March 31 18:00 UTC
| |
17:59 | se6ast1an | my recent progress, mostly doing CAD improvements and new parts for the AXIOM Beta compact enclosure
| |
17:59 | se6ast1an | https://cloud.apertus.org/index.php/apps/gallery/s/LqkCfTLRJYd9wFB#PCB%20Holding%20Bracket
| |
17:59 | se6ast1an | https://cloud.apertus.org/index.php/apps/gallery/s/LqkCfTLRJYd9wFB#Nato%20Rail%20Concept
| |
18:00 | se6ast1an | manfred currently has the CP prototype for disassembly/assembly review
| |
18:00 | se6ast1an | so small changes/improvements based on his feedback soon maybe
| |
18:00 | BAndiT1983 | CP?
| |
18:00 | se6ast1an | AXIOM Beta Compact = AXIOM Beta CP or ABCP
| |
18:00 | BAndiT1983 | ah
| |
18:01 | se6ast1an | thats it from me
| |
18:01 | se6ast1an | anyone else? otherwise meeting concluded, great that so many people attended today!
| |
18:01 | se6ast1an | thank you all for being here and pushing things forward!
| |
18:04 | max_bxl | thank you se6ast1an for organizing the meetings !
| |
18:04 | se6ast1an | my pleasure!
| |
18:31 | RexOrCine | joined the channel | |
18:47 | max_bxl | quick question regarding dcnuframe-x1.pgm and darkframe-x1.pgm
| |
18:47 | max_bxl | they just need to be in the directory from where I run raw2dng right ?
| |
18:48 | max_bxl | is there a way to specify where they are ?
| |
18:48 | max_bxl | (ie indicating a path and not copy/paste them in the working directory)
| |
18:51 | Bertl | no idea but you could always use a symlink?
| |
18:53 | max_bxl | will try
| |
18:54 | max_bxl | I see no difference (zoom 200%) between the DNG made with the dcnuframe-x1.pgm and darkframe-x1.pgm and the one without...
| |
18:57 | SierraSkye | joined the channel | |
18:59 | RexOrCine | left the channel | |
19:01 | SierraSkye | left the channel | |
19:06 | se6ast1an | max_bxl: does the raw2dng process say that the darkframe was used?
| |
19:06 | se6ast1an | do you still see no difference if you increase contrast drastically in the raw development suite
| |
19:13 | max_bxl | se6ast1an: raw2dng says nothing, will try the "high contrast" test
| |
19:15 | max_bxl | looks exactly the same...
| |
19:17 | max_bxl | by the way, you can have a look at the output here : https://cloud.apertus.org/index.php/s/tteXjjYTN8Czt3D
| |
19:17 | max_bxl | (with a nice 2sec video file !)
| |
19:18 | max_bxl | how to know if raw2dng used dcnuframe-x1.pgm and darkframe-x1.pgm ?
| |
19:20 | Bertl | off for now ... bbl
| |
19:20 | Bertl | changed nick to: Bertl_oO
| |
19:29 | max_bxl | AFK for now, bye!
| |
19:34 | Spirit532 | left the channel | |
19:35 | Spirit532 | joined the channel | |
19:36 | se6ast1an | max_bxl: I thought raw2dng writes what it does and lists what it uses or cant find
| |
19:37 | se6ast1an | 2 seconds of video looks good!
| |
19:43 | aombk2 | left the channel | |
19:44 | aombk | joined the channel | |
22:16 | se6ast1an | off to bed
| |
22:16 | se6ast1an | good night
| |
22:16 | preetimenghwani[ | Good night!
| |
22:29 | BAndiT1983 | changed nick to: BAndiT1983|away
| |
22:51 | berto_bxl | left the channel | |
23:12 | max_bxl | off to bed, bye everyone_
| |
23:12 | max_bxl | left the channel | |
23:13 | Spirit532 | left the channel | |
23:16 | Spirit532 | joined the channel |