Posts
4634
Following
317
Followers
482
Linux kernel hacker and maintainer etc.

OpenPGP: 3AB05486C7752FE1

Jarkko Sakkinen

Edited 1 year ago
software products of finnish software company arisoft. it is fun observation that the whole serial link thing that they had on-going is generation over what people use today when they connect TTL-USB-cable. Arisoft had a MS-DOS software in the early 90s that made possible to "smurf" your way in through the serial and have simultaneous file transfer at the same time. multitasking is imho the future.

so when i look at this web page i'm literally not looking into the past but to one generation ahead in the hopefully not so distant future.

#zmodem #smodem #bbs #serial #tty
1
0
2
@monsieuricon is there any plans to have some tool level interaction with kernel bugzilla? that is sort of forum that gets easily disregarded because LKML is the top priority. with better tooling it would be easier to provide better service. right now the bugzilla feels sort of separate island where you have to take a boat to visit and do your business, and then come back to the mainland.
1
0
0
should start using patchwork again for a test run. had totally forgotten its existence not to disregard its usefulness. since i use b4 already with lore, i'll test run this for a some patch set under review, thanks for reminder :-)
1
0
0

Jarkko Sakkinen

Edited 1 year ago
so the way to differentiate from other offerings here is for me to just not make generic xyzmodem crate but just focus on fluent zmodem binary transmit. and for further support disregard any other features except binary link level stuff that makes sense to modern SBC's. still makes the interface just generic enough to later on support SMODEM style multiplexing where the bandwidth can be shared with file transfers and an interactive session.

so the scope is anything that helps with the transport layer and not carry any corpse protocols.

just using this as a tool to put some notes as this thing keeps developing :-) i'll try to get zcbin first work in my tior serial tool concept (GPL2) and later on detach the protocol part to a MIT or similar licensed crate.
0
0
0

i guess i could create a completely new crate to the crate ecosystem called rmodem with initially just with ZCBIN implementation but sort of BufReader/Writer approach towards integration.

1
0
0
i mean being able to transfer files and have full access to tty session through serial is a great goal which would help a lot dealing with all sorts of development boards. comes totally from practical needs.
1
0
1
and like additional development from this would be to do something like https://en.wikipedia.org/wiki/SMODEM, which would allow have a TTY session and concurrent file transfer simultaneously from the same serial cable, which would be enormous improvement. but yeah this part requires already diverging from original zmodem so let's get that right first.
1
0
1

Jarkko Sakkinen

Edited 1 year ago
My online life started about then in the BBS world first and I've yet to meet a person who willingly uses xmodem or ymodem for anything. I would be more eager to try out stuff that promotes explicitly to support neither. they were already corpses when i first discovered of their existence.

you *literally* need to visit maybe a rest home to meet a living person who has ever had any profitalble use for them...

on the other hand zmodem is still a thing with SBC's and FPGA's.
1
0
1
Tbh, I don't really get why people have done new kermit/minicom style programs and promote X-modem and Y-modem, which nobody used even in 1993 when calling BBS's because they were so terrible. Why not then just use kermit. or minicom instead. I want to sort of well integrated "zmodem experience" :-)
1
0
0
And make it sort of maybe BufReader/Writer style thing so that it has no understanding of its surroundings... yea, i think i have a solid plan carved up
1
0
0
I.e. just ZCBIN ignoring all 16-bit legacy and other BBS'esque clutter. fun little exercise to accomplish i guess
1
0
0

Jarkko Sakkinen

it is 2023 and i'm implementing #zmodem just a sub-portion of it: 32-bit binary transfers. So ignoring 16-bit and alternative hex protocol. There's some non lively looking zmodem crate and of course lrzsz but neither of them feel too inspiring to contribute or build on top off.
1
0
1

Jarkko Sakkinen

Edited 1 year ago
Rust is robust in the sense how it can respond to different memory safety issues but it is robust to the limits "as long as you accept the default response". If you don't agree with the response, there's way to go around it but is sort of "not recommended for most". It is a bit like you would limit email only pre-defined template responses.

So the stimulus part of the safe systems programming language equation is gotten right but hard coded response as defaults is not a great thing tbh.
1
0
0
Unrobust meaning that you can do all of this but would have to put unrealistic amount of effort to accomplish any possible e,g. business or even academic goals.
1
0
1

Jarkko Sakkinen

all sort of glitch with #rustlang community comes to personally in the end how you look at a programming language: a language or purely just an opcode generator. one example of such glitch is IMHO unrobust handling of OOM conditions. So you end up getting safe but and super fat and resource wasteful user space programs. But still memory-safe in the language level, which does not provide safety for e.g. any possible DoS attack.
1
0
1

Jarkko Sakkinen

tonights jam, something in progress #bitwig
0
0
0
@laund implement even a PoC quality version of SBI on top of Embassy. Then I'm super interested. Even just bare bones baseline for development an something is provably in working condition. There's some dead looking SBI crate but I would see more future in implementing one top of this more or less accepted framework called Embassy I suppose. Not that I'm too familiar with that either. I just hack CPU's, that what I do in the end....
0
0
0
@laund AFAIK does not provide SBI implementation (could be wrong too) so not really what I was looking after.
1
0
0

Jarkko Sakkinen

Lot's of RISC-V posts but here's one more. I think it has a strong future in post-#quantum world. QPU is like GPU, i.e. it is great for certain types of computations but it sucks for branching binary logic that I/O relies on. In that world correctness of stuff that is done with semiconductors is hugely more important than now and that's where open, modular and within constraints formally verifiable CPU architecture shines.

#riscv
0
0
2

Jarkko Sakkinen

If most of firmware stack in RISC-V was rustified so that you could build compatible SBI implementation with cargo build, that would be the most effective embedded product creation platform that I could think of. You could move from product idea rapidly to a product PoC.

#riscv #rustlang
2
3
6
Show older