*** tpb <[email protected]> has joined #symbiflow | 00:00 | |
*** rvalles <rvalles!~rvalles@user/rvalles> has quit IRC (Read error: Connection reset by peer) | 02:36 | |
*** rvalles <rvalles!~rvalles@user/rvalles> has joined #symbiflow | 02:36 | |
*** TMM_ <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 06:56 | |
*** TMM_ <[email protected]> has joined #symbiflow | 06:56 | |
sf-slack | <mkurc> Hi @xanjohns. I'll have a look into it today. | 07:09 |
---|---|---|
*** balrog <balrog!znc@user/balrog> has quit IRC (Ping timeout: 240 seconds) | 11:31 | |
*** balrog <balrog!znc@user/balrog> has joined #symbiflow | 11:52 | |
*** TMM_ <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 15:23 | |
*** TMM_ <[email protected]> has joined #symbiflow | 15:23 | |
benreynwar | Could someone familiar with prjxray give me a one sentence explanation for each of the tools in the tools directory? | 15:37 |
benreynwar | The tools are bitread, bittool, segmatch, gen_part_base_yaml, xc7path, xc7frames2bit, frame_address_decoder, bits2rbt | 15:38 |
benreynwar | I'll use this info to improve docs/db_dev_process/parts.rst | 15:40 |
sf-slack | <acomodi> Hi, benreynwar | 15:43 |
benreynwar | acomdi: Hi! | 15:45 |
sf-slack | <acomodi> bitread is used to read a bitstream file to output a readable bitfile that can be than used to get the various FASM features | 15:45 |
sf-slack | <acomodi> segmatch is mainly used in the fuzzing process to correlate the different bits and find which one belong to which feature | 15:46 |
sf-slack | <acomodi> gen_part_base_yaml is used to get a high level information on the device structure (number of configuration rows/columns and maximum frame addresses) | 15:47 |
sf-slack | <acomodi> xc7frames2bit is used to write a bitstream file starting from a frames one. Where, in turn, the frames file can be generated starting from a FASM file | 15:47 |
sf-slack | <acomodi> xc7patch is used to patch a pre-existing bitstream with additional bits | 15:48 |
mithro | acomodi: The new prjxray-db has been pushed! | 15:52 |
sf-slack | <acomodi> mithro: great, thanks :) | 15:52 |
benreynwar | acomodi: If any of them aren't really used much, then don't bother explaining them to me. | 15:53 |
benreynwar | Those explanations will save me a bunch of time making sense of things. Thanks! | 15:53 |
sf-slack | <acomodi> No problem, I am not sure about bittool and bits2rbt, as they are not really used that much | 15:57 |
mithro | benreynwar: It would be great if that was turned into documentation if it isn't already! | 18:38 |
benreynwar | acomodi: Another quick question. If I look at a segdata* file, then I see "seg 00000000_026" and "bit 38_106". What do 00000000, 26, 38 and 106 refer to? | 18:38 |
mithro | benreynwar: BTW Long time no see! :-) | 18:38 |
benreynwar | mithro: Yep, I've already got it on as documentation on an internal branch, but it'll probably be next week before I'm sure I'm got to push things publicly that I've done at work. | 18:38 |
benreynwar | mithro: Yep. Good to see. Nice to be able to work on this stuff during work time now :). Sounds like there aren't going to be any issues committing things publicly, but I want to double check first seeing as I'm new. | 18:40 |
mithro | benreynwar: Want to send me an email to [email protected] or [email protected] about what you are doing? | 18:46 |
mithro | xanjohns: I think the biggest thing to think about the common-config stuff is that you are not going to finish moving everything, so we need to have a handoff procedure and otherwise good documentation of the plan so it can be continued when you go back to normal school work | 18:47 |
benreynwar | mithro: Will do. I'm pretty sure you're already in touch with the group I've just joined. | 18:52 |
mithro | benreynwar: Can't hurt to have more contact :-) | 18:53 |
mithro | I also lose track of things all the time :-) | 18:53 |
benreynwar | mithro: I was actually impressed you recognized my name, give how few times we've interacted :). | 18:59 |
benreynwar | I think I lost acomodi to the European evening. Anybody else know how to interpret the "seg 00000000_026" and "bit 38_106" in a prjxray segdata file? | 19:32 |
gatecat | it's been a while but I think the second one is frame_bit | 19:51 |
gatecat | benreynwar: ^ | 19:52 |
benreynwar | gatecat: Thanks. | 19:54 |
benreynwar | Turns out my colleague Ian Taras knows this stuff pretty well, so he explained it to me. I'll see if it makes sense to add this to the documentation as well. | 20:17 |
gatecat | I think improving the docs is always helpful | 20:19 |
sf-slack | <pgielda> PRs to documentation are always welcome | 20:33 |
mithro | Yeap! | 22:34 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!