And I have to say the way you are confusing those things sounds to me very much like you are rationalizing at best or gaslighting at worst, not like you are trying to make a good faith argument.
-
-
Replying to @oe1cxw @whitequark and
I started my argumentation withpic.twitter.com/VcesU36p9h
1 reply 0 retweets 0 likes -
Replying to @dcuartielles @oe1cxw and
I might be mistaken, I haven't checked in the last year or so, but Lattice's parts aren't open hardware. On the other hand, for Arduino it is very important to be sure that the efforts we make when manufacturing boards (and we make many boards) are backed by part availabilty
2 replies 0 retweets 1 like -
Replying to @dcuartielles @oe1cxw and
please show me a single Atmel, ST, or Intel chip that is open hardware
2 replies 0 retweets 4 likes -
Replying to @whitequark @oe1cxw and
sure, but I thought this was not the discussion, or was it? I was just pointing it out ;-)
3 replies 0 retweets 0 likes -
Replying to @dcuartielles @whitequark and
From the project survival point of view, and from the perspective of being able of serving as many people as possible, our approach has been making a hw agnostic toolchain. The same that Verilog or VHDL tools are for FPGAs.
1 reply 0 retweets 1 like -
Replying to @dcuartielles @whitequark and
So, while the ICE approach has been making a tool that works on certain hardware that had to be hacked, our hack was to make a toolchain that runs on anything programmed in C. And then we can go on an endless rant about how open is open or that is more open.
2 replies 0 retweets 0 likes -
Replying to @dcuartielles @whitequark and
A lot of this discussion seems like it's based on a misconception. The open toolchains don't use any exploits or clever tricks to run bitstreams on these FPGAs. Instead, it was just discovered what the bits in the FPGA configuration mean, so open source tools can configure them.
1 reply 0 retweets 5 likes -
Replying to @ktemkin @whitequark and
I agree with this, this is my definition of "hacking" It is not like there was a datasheet people had access to and could use to write the tool to do the bitstream generation or was it? I think this shows a tremendous skill and I totally respect that, I wish I had done it :-)
2 replies 0 retweets 2 likes -
Replying to @dcuartielles @ktemkin and
What I would like to have is a datasheet from whatever manufacturer backing up the work and opening up for anyone to make the port to their hardware. I wish this will happen sooner than later.
2 replies 0 retweets 1 like
(1) that's not what "open source" means (2) and the vendor of the part you are using now provides this kind of documentation? because the whole point is irrelevant if you then went for a part that is not documented by he vendor in this way.
-
-
(1) open source according to what definition. It we talk open source hardware CERN definition, I think having the files of how things are built are the minimum requirement (I was there writing the initial freedoms) (2) microcontrollers offer what they offer and we hack them
2 replies 0 retweets 2 likes -
Replying to @dcuartielles @oe1cxw and
Can I suggest we maybe leave this aspect of discussion be? I'm not sure there's much to be gained in arguing semantics. I like the idea of trying to find ways to move forward; I'm less keen on examining past decisions or what words mean. If debate continues, please un-@ me?
1 reply 0 retweets 2 likes - Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.