myhdl-list Mailing List for MyHDL (Page 174)
Brought to you by:
jandecaluwe
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(14) |
Nov
(4) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(1) |
Feb
(10) |
Mar
(19) |
Apr
(14) |
May
(1) |
Jun
(4) |
Jul
(10) |
Aug
|
Sep
(2) |
Oct
(7) |
Nov
(17) |
Dec
(12) |
| 2005 |
Jan
(6) |
Feb
(10) |
Mar
(17) |
Apr
(10) |
May
(9) |
Jun
(5) |
Jul
(26) |
Aug
(34) |
Sep
(10) |
Oct
(38) |
Nov
(71) |
Dec
(74) |
| 2006 |
Jan
(20) |
Feb
(20) |
Mar
(7) |
Apr
(2) |
May
(13) |
Jun
|
Jul
|
Aug
(4) |
Sep
(37) |
Oct
(43) |
Nov
(30) |
Dec
(33) |
| 2007 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
(30) |
Jun
(9) |
Jul
(1) |
Aug
|
Sep
(8) |
Oct
(13) |
Nov
|
Dec
(4) |
| 2008 |
Jan
(13) |
Feb
(46) |
Mar
(25) |
Apr
(7) |
May
(20) |
Jun
(73) |
Jul
(38) |
Aug
(47) |
Sep
(24) |
Oct
(18) |
Nov
(9) |
Dec
(36) |
| 2009 |
Jan
(31) |
Feb
(24) |
Mar
(73) |
Apr
(13) |
May
(47) |
Jun
(28) |
Jul
(36) |
Aug
(2) |
Sep
(5) |
Oct
(8) |
Nov
(16) |
Dec
(29) |
| 2010 |
Jan
(34) |
Feb
(18) |
Mar
(18) |
Apr
(5) |
May
|
Jun
(24) |
Jul
(53) |
Aug
(3) |
Sep
(18) |
Oct
(33) |
Nov
(19) |
Dec
(15) |
| 2011 |
Jan
(9) |
Feb
(4) |
Mar
(39) |
Apr
(213) |
May
(86) |
Jun
(46) |
Jul
(22) |
Aug
(11) |
Sep
(78) |
Oct
(59) |
Nov
(38) |
Dec
(24) |
| 2012 |
Jan
(9) |
Feb
(22) |
Mar
(89) |
Apr
(55) |
May
(222) |
Jun
(86) |
Jul
(57) |
Aug
(32) |
Sep
(49) |
Oct
(69) |
Nov
(12) |
Dec
(35) |
| 2013 |
Jan
(67) |
Feb
(39) |
Mar
(18) |
Apr
(42) |
May
(79) |
Jun
(1) |
Jul
(19) |
Aug
(18) |
Sep
(54) |
Oct
(79) |
Nov
(9) |
Dec
(26) |
| 2014 |
Jan
(30) |
Feb
(44) |
Mar
(26) |
Apr
(11) |
May
(39) |
Jun
(1) |
Jul
(89) |
Aug
(15) |
Sep
(7) |
Oct
(6) |
Nov
(20) |
Dec
(27) |
| 2015 |
Jan
(107) |
Feb
(106) |
Mar
(130) |
Apr
(90) |
May
(147) |
Jun
(28) |
Jul
(53) |
Aug
(16) |
Sep
(23) |
Oct
(7) |
Nov
|
Dec
(16) |
| 2016 |
Jan
(86) |
Feb
(41) |
Mar
(38) |
Apr
(31) |
May
(37) |
Jun
(11) |
Jul
(1) |
Aug
(1) |
Sep
(3) |
Oct
(1) |
Nov
(5) |
Dec
(3) |
| 2017 |
Jan
|
Feb
(4) |
Mar
(2) |
Apr
(2) |
May
|
Jun
(3) |
Jul
(2) |
Aug
(2) |
Sep
(1) |
Oct
(2) |
Nov
(1) |
Dec
(1) |
| 2018 |
Jan
(1) |
Feb
(1) |
Mar
(7) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
(1) |
May
(1) |
Jun
(2) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(3) |
Dec
|
| 2020 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
(3) |
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
(12) |
Dec
(11) |
| 2022 |
Jan
(7) |
Feb
(2) |
Mar
(1) |
Apr
|
May
|
Jun
(1) |
Jul
(3) |
Aug
(2) |
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
| 2023 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2024 |
Jan
(1) |
Feb
(2) |
Mar
(4) |
Apr
(2) |
May
(2) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
(2) |
| 2025 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
|
From: George P. <ge...@ga...> - 2006-03-10 22:25:13
|
Wow, I think this will be very useful to me. Especially the py.test part. I've been invited to present my music synthesizer project to a graduate class in a few weeks, and I really would like to showcase the agile development angle of things. So having this cookbook soon will definitely help :) George > Hi: > > For some time now, I'm working (and staring) on this new cookbook page: > > http://myhdl.jandecaluwe.com/doku.php/cookbook:stopwatch > > I have all elements in place, but I'm not making progress > with finalizing the story, a writer's block perhaps :-) > > This page is supposed to tell a lot of things. Basically it > does the Xilinx ISE tutorial in the MyHDL way, uses py.test for unit > testing, and goes all the way to synthesis and implementation. > > When done, I want to announce it in comp.arch.fpga. > > Ok, I hope this announcement will break it :-) > > Jan > |
|
From: Jan D. <ja...@ja...> - 2006-03-10 22:02:08
|
Hi:
For some time now, I'm working (and staring) on this new cookbook page:
http://myhdl.jandecaluwe.com/doku.php/cookbook:stopwatch
I have all elements in place, but I'm not making progress
with finalizing the story, a writer's block perhaps :-)
This page is supposed to tell a lot of things. Basically it
does the Xilinx ISE tutorial in the MyHDL way, uses py.test for unit
testing, and goes all the way to synthesis and implementation.
When done, I want to announce it in comp.arch.fpga.
Ok, I hope this announcement will break it :-)
Jan
--
Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
Losbergenlaan 16, B-3010 Leuven, Belgium
From Python to silicon:
http://myhdl.jandecaluwe.com
|
|
From: Jan D. <ja...@ja...> - 2006-03-06 23:02:54
|
George Pantazopoulos wrote:
> Hi all,
>
> In general for state machines is it a must to specify all the outputs
> at every state? Sometimes I just want an output to stay the same until I
> explicitly tell it to change, which seems necessary sometimes, and also
> results in more readable code. However, is this advisable?
There is no technical reason to do anything else than keeping the
code as readable as possible. The "state machine" paradigm is somewhat
outdated with modern HDLs and synthesis. Keeping a signal to its value
is implemented as efficiently as giving it a specific value.
A related issue is when you want to specify the same value for an
output most of the time, and another one in a specific state (and
perhaps under special conditions) only. Use a default value in
that case:
sig.next = <default value>
if state == ...
...
elif state == ...
...
if <special case>:
sig.next = <special value>
elif ...
...
else:
...
Jan
--
Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
Losbergenlaan 16, B-3010 Leuven, Belgium
From Python to silicon:
http://myhdl.jandecaluwe.com
|
|
From: George P. <ge...@ga...> - 2006-02-28 07:42:12
|
Hi all,
In general for state machines is it a must to specify all the
outputs at every state? Sometimes I just want an output to stay the same
until I explicitly tell it to change, which seems necessary sometimes,
and also results in more readable code. However, is this advisable?
Thanks,
George
|
|
From: Jan D. <ja...@ja...> - 2006-02-26 19:34:59
|
George Pantazopoulos wrote: > Hi all, > > I recently greatly upgraded the PhoenixSID music synthesizer I've been > working on, and added some more sounds to the webpage: Congratulations with the progress. Personally I would be quite interested in getting more insight in size and complexity of the MyHDL part e.g. nr of hardware modules, lines of code, size of Verilog output file, FPGA synthesis and map report highlights. Regards, Jan -- Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com Losbergenlaan 16, B-3010 Leuven, Belgium From Python to silicon: http://myhdl.jandecaluwe.com |
|
From: George P. <ge...@ga...> - 2006-02-25 20:15:55
|
Hi all, I recently greatly upgraded the PhoenixSID music synthesizer I've been working on, and added some more sounds to the webpage: http://myhdl.jandecaluwe.com/doku.php/projects:phoenixsid_65x81 PS. Thanks to the MyHDL community for your support Enjoy, George |
|
From: Jan D. <ja...@ja...> - 2006-02-25 07:50:36
|
George Pantazopoulos wrote:
> Hi Jan,
>
> Could you add a check for accidental use of "signal.next == value"
> instead of "signal.next = value" ? It saves time to have it caught at
> the myHDL level.
This is the type of problem (not specific to MyHDL) that pychecker
can find:
http://pychecker.sourceforge.net/
I don't use pychecker regularly, but I think I should. Also, it
might be useful to come up with some settings for the MyHDL
case (e.g. to ignore the myhdl package itself).
Jan
--
Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
Losbergenlaan 16, B-3010 Leuven, Belgium
From Python to silicon:
http://myhdl.jandecaluwe.com
|
|
From: George P. <ge...@ga...> - 2006-02-25 01:15:35
|
Hi Jan, Could you add a check for accidental use of "signal.next == value" instead of "signal.next = value" ? It saves time to have it caught at the myHDL level. Thanks, George |
|
From: George P. <ge...@ga...> - 2006-02-13 05:27:51
|
Hi Jan,
When the time is right, don't forget to establish a presence on
Wikipedia (eg, a myHDL page with links in the CPLD/FPGA related pages).
George
|
|
From: Haitao Z. <ha...@gm...> - 2006-02-08 17:16:05
|
Jan, Thank you very much for the reference and the example. It is a very elegant solution. Haitao On 2/8/06, Jan Decaluwe <ja...@ja...> wrote: > > Haitao Zhang wrote: > > > > Does myHDL now support signed vector and how? > > It has always been possible to use negative intbv's - but until > 0.5 it was not possible to convert them to Verilog. I assume > that's what you mean. Signed support for Verilog conversion > in 0.5 is described here: > > > http://myhdl.jandecaluwe.com/doku.php/whatsnew:0.5#support_for_signed_ari= thmetic > > > Without signed number support specifying a signed multiplication (or > > other arithmetics) is quite awkward. It is also non-optimal for > synthesis. > > I'll give an example to clarify. Consider: > > > from myhdl import * > > def test(c, a, b): > > @always_comb > def mult(): > c.next =3D a * b > > return mult > > > to describe a multiplication. As always, you can convert a > design instance to Verilog. For negative intbv's you have to > constrain them using an integer range, not a bit slice. Note > that this is higher level view than working with bit vectors, > entirely appropriate for arithmetic and much less error-prone. > For example: > > a =3D Signal(intbv(0, min=3D-9, max=3D45)) > b =3D Signal(intbv(0, min=3D-24, max=3D45)) > c =3D Signal(intbv(0, min=3D-1000, max=3D1000)) > > toVerilog(test, c, a, b) > > The Verilog output is: > > module test ( > c, > a, > b > ); > > output signed [10:0] c; > wire signed [10:0] c; > input signed [6:0] a; > input signed [6:0] b; > > assign c =3D (a * b); > > endmodule > > > Note how signed regs are used. Now, consider a > different conversion: > > a =3D Signal(intbv(0, min=3D0, max=3D45)) > b =3D Signal(intbv(0, min=3D-24, max=3D45)) > c =3D Signal(intbv(0, min=3D-1000, max=3D1000)) > > toVerilog(test, c, a, b) > > Then the output is: > > module test ( > c, > a, > b > ); > > output signed [10:0] c; > wire signed [10:0] c; > input [5:0] a; > input signed [6:0] b; > > assign c =3D ($signed({1'b0, a}) * b); > > endmodule > > Now the convertor uses an unsigned reg for a, but adds a > sign bit and a cast to it in the multiplication. It's for this reason > that I claim that working with negative numbers is much easier > in MyHDL than in Verilog: the error-prone issues with regard to > signed representation are taken care of by the convertor. > > Ain't it great :-)? > > Jan > > > -- > Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com > Losbergenlaan 16, B-3010 Leuven, Belgium > From Python to silicon: > http://myhdl.jandecaluwe.com > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat= =3D121642 > _______________________________________________ > myhdl-list mailing list > myh...@li... > https://lists.sourceforge.net/lists/listinfo/myhdl-list > |
|
From: Jan D. <ja...@ja...> - 2006-02-08 10:56:42
|
Haitao Zhang wrote: > > Does myHDL now support signed vector and how? It has always been possible to use negative intbv's - but until 0.5 it was not possible to convert them to Verilog. I assume that's what you mean. Signed support for Verilog conversion in 0.5 is described here: http://myhdl.jandecaluwe.com/doku.php/whatsnew:0.5#support_for_signed_arithmetic > Without signed number support specifying a signed multiplication (or > other arithmetics) is quite awkward. It is also non-optimal for synthesis. I'll give an example to clarify. Consider: from myhdl import * def test(c, a, b): @always_comb def mult(): c.next = a * b return mult to describe a multiplication. As always, you can convert a design instance to Verilog. For negative intbv's you have to constrain them using an integer range, not a bit slice. Note that this is higher level view than working with bit vectors, entirely appropriate for arithmetic and much less error-prone. For example: a = Signal(intbv(0, min=-9, max=45)) b = Signal(intbv(0, min=-24, max=45)) c = Signal(intbv(0, min=-1000, max=1000)) toVerilog(test, c, a, b) The Verilog output is: module test ( c, a, b ); output signed [10:0] c; wire signed [10:0] c; input signed [6:0] a; input signed [6:0] b; assign c = (a * b); endmodule Note how signed regs are used. Now, consider a different conversion: a = Signal(intbv(0, min=0, max=45)) b = Signal(intbv(0, min=-24, max=45)) c = Signal(intbv(0, min=-1000, max=1000)) toVerilog(test, c, a, b) Then the output is: module test ( c, a, b ); output signed [10:0] c; wire signed [10:0] c; input [5:0] a; input signed [6:0] b; assign c = ($signed({1'b0, a}) * b); endmodule Now the convertor uses an unsigned reg for a, but adds a sign bit and a cast to it in the multiplication. It's for this reason that I claim that working with negative numbers is much easier in MyHDL than in Verilog: the error-prone issues with regard to signed representation are taken care of by the convertor. Ain't it great :-)? Jan -- Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com Losbergenlaan 16, B-3010 Leuven, Belgium From Python to silicon: http://myhdl.jandecaluwe.com |
|
From: Haitao Z. <ha...@gm...> - 2006-02-08 00:19:47
|
Does myHDL now support signed vector and how? Without signed number support specifying a signed multiplication (or other arithmetics) is quite awkward. It is also non-optimal for synthesis. Thanks, Haitao |
|
From: George P. <ge...@ga...> - 2006-02-07 13:43:38
|
Thanks Jan! I think I will be announcing there in the not-too-distant future. By the way, in the XGameStation forum, Andre' Lamothe (hacker, author, and owner of the company) asked a good question about the efficiency of myHDL. If you want to reply,the post is: http://205.158.110.70/ubbcgi/ultimatebb.cgi?ubb=get_topic&f=20&t=001225 There's a very cool hardware-hacking community on that site! George > Jan Decaluwe wrote: >> George Pantazopoulos wrote: >> >>> Hi all, >>> >>> I'm pleased to have some early sound samples to post to the >>> PhoenixSID project page. This project is a joy to work on, thanks >>> for helping to make it possible! >> >> >> Congratulations George, I can hear you :-) >> >> Why not announce your project in comp.lang.fpga? I'm pretty sure >> you'll have a very interested audience over there. > > Correction: that should have been comp.arch.fpga. Quite an > active newsgroup with fpga users and vendors, often discussing > relevant problems :-) > > Jan > |
|
From: Jan D. <ja...@ja...> - 2006-02-07 08:41:24
|
Jan Decaluwe wrote: > George Pantazopoulos wrote: > >> Hi all, >> >> I'm pleased to have some early sound samples to post to the >> PhoenixSID project page. This project is a joy to work on, thanks for >> helping to make it possible! > > > Congratulations George, I can hear you :-) > > Why not announce your project in comp.lang.fpga? I'm pretty sure > you'll have a very interested audience over there. Correction: that should have been comp.arch.fpga. Quite an active newsgroup with fpga users and vendors, often discussing relevant problems :-) Jan -- Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com Losbergenlaan 16, B-3010 Leuven, Belgium From Python to silicon: http://myhdl.jandecaluwe.com |
|
From: Jan D. <ja...@ja...> - 2006-02-07 08:35:49
|
George Pantazopoulos wrote: > Hi all, > > I'm pleased to have some early sound samples to post to the > PhoenixSID project page. This project is a joy to work on, thanks for > helping to make it possible! Congratulations George, I can hear you :-) Why not announce your project in comp.lang.fpga? I'm pretty sure you'll have a very interested audience over there. Jan -- Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com Losbergenlaan 16, B-3010 Leuven, Belgium From Python to silicon: http://myhdl.jandecaluwe.com |
|
From: George P. <ge...@ga...> - 2006-02-07 04:38:22
|
Hi all,
I'm pleased to have some early sound samples to post to the
PhoenixSID project page. This project is a joy to work on, thanks for
helping to make it possible!
http://myhdl.jandecaluwe.com/doku.php/projects:phoenixsid_65x81
George
|
|
From: Jan D. <ja...@ja...> - 2006-02-06 16:21:24
|
George Pantazopoulos wrote: > Excellent idea. How about adding the missing automated unit tests that we > all know and love? :) And yeah, they're important, you were right about > coming back to a project after a vacation and needing the assurance of > automated tests :) There you have it, my own preaching is backfiring :-) Ok - I maintain the position that unit tests should be written for every module, even if the test seems trivial. Now, in this case, the modules themselves are artificially simple and actually trivial - as I note in the intro, you normally wouldn't describe individual flip-flops. (Or at least, I wouldn't). The page is intended to let people make quick comparisons with other HDLs, using things they know that require no explanation. (I use the opportunity to demonstrate waveform tracing to let them know it's there). For a meaningful unit test, you try to approach the circuit from some different angle at a (perhaps slightly) higher level. In this case, I don't think there's anything else one can do than simply copying the implementation. So I fear that people won't see the point here, and the message may get lost. However - I'm working on another page :-) that should clearly illustrate the whole flow. I'm actually using the Xilinx ISE tutorial and redoing it the "MyHDL way". It will show unit tests, ROM inferencing, synthesis and retargeting to various FPGA/CPLD technologies - so I think this is going to be an interesting page. Jan -- Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com Losbergenlaan 16, B-3010 Leuven, Belgium From Python to silicon: http://myhdl.jandecaluwe.com |
|
From: Jan D. <ja...@ja...> - 2006-02-06 11:26:01
|
George Pantazopoulos wrote: > Hi Jan, > > I think application/octet-stream would work, based on RFC 2046 (section > 4.3). > I should work now, I used audio/mpeg and application/ogg anyway as these seem to be the right mime types. Jan -- Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com Losbergenlaan 16, B-3010 Leuven, Belgium From Python to silicon: http://myhdl.jandecaluwe.com |
|
From: George P. <ge...@ga...> - 2006-02-06 02:02:52
|
Hi Jan, I think application/octet-stream would work, based on RFC 2046 (section 4.3). Thanks, George > George Pantazopoulos wrote: >> Hi Jan, >> >> I'm trying to upload some sound samples to the wiki, but it tells >> my that the mp3 filetype is forbidden. Would you please allow this >> (and .ogg)? > > That's possible, but I need the mime type. > What should the mime type for these extensions be? I looked around > and I found a whole number of alternatives. Or should it just > be a generic application/octetstream? > > Jan > |
|
From: Jan D. <ja...@ja...> - 2006-02-05 21:21:36
|
George Pantazopoulos wrote: > Hi Jan, > > I'm trying to upload some sound samples to the wiki, but it tells my > that the mp3 filetype is forbidden. Would you please allow this (and .ogg)? That's possible, but I need the mime type. What should the mime type for these extensions be? I looked around and I found a whole number of alternatives. Or should it just be a generic application/octetstream? Jan -- Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com Losbergenlaan 16, B-3010 Leuven, Belgium From Python to silicon: http://myhdl.jandecaluwe.com |
|
From: George P. <ge...@ga...> - 2006-02-05 17:51:49
|
Hi Jan, I'm trying to upload some sound samples to the wiki, but it tells my that the mp3 filetype is forbidden. Would you please allow this (and .ogg)? Thanks, George |
|
From: George P. <ge...@ga...> - 2006-02-03 17:42:10
|
Excellent idea. How about adding the missing automated unit tests that we all know and love? :) And yeah, they're important, you were right about coming back to a project after a vacation and needing the assurance of automated tests :) George > Hi: > > I am working on additional cookbook pages. > > There was a suggestion to add simple examples before > adding more complex ones. Accordingly, I have created > a page about flip-flops and latches: > > http://myhdl.jandecaluwe.com/doku.php/cookbook:ff > > Jan > > -- > Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com > Losbergenlaan 16, B-3010 Leuven, Belgium > From Python to silicon: > http://myhdl.jandecaluwe.com > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat= =3D121642 > _______________________________________________ > myhdl-list mailing list > myh...@li... > https://lists.sourceforge.net/lists/listinfo/myhdl-list > --=20 George Pantazopoulos http://www.gammaburst.net |
|
From: Jan D. <ja...@ja...> - 2006-02-03 11:36:55
|
Hi: I am working on additional cookbook pages. There was a suggestion to add simple examples before adding more complex ones. Accordingly, I have created a page about flip-flops and latches: http://myhdl.jandecaluwe.com/doku.php/cookbook:ff Jan -- Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com Losbergenlaan 16, B-3010 Leuven, Belgium From Python to silicon: http://myhdl.jandecaluwe.com |
|
From: nicran <ni...@gm...> - 2006-01-25 03:55:45
|
Jan, I've already read that article, great work! 2006/1/24, Jan Decaluwe <ja...@ja...>: > > Hi all: > > MyHDL is in the news today at http://www.eetimes.com. > > I had asked Richard Goering to add a link in their open-source > tool list, and he found it interesting enough for a story. > He wrote the article based on a telephone interview. It's very > well written, clear and complete. I have told him that I > understand it better now :-) > > Regards, > > Jan > > -- > Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com > Losbergenlaan 16, B-3010 Leuven, Belgium > From Python to silicon: > http://myhdl.jandecaluwe.com > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat= =3D121642 > _______________________________________________ > myhdl-list mailing list > myh...@li... > https://lists.sourceforge.net/lists/listinfo/myhdl-list > |
|
From: Jan D. <ja...@ja...> - 2006-01-24 07:42:21
|
Hi all: MyHDL is in the news today at http://www.eetimes.com. I had asked Richard Goering to add a link in their open-source tool list, and he found it interesting enough for a story. He wrote the article based on a telephone interview. It's very well written, clear and complete. I have told him that I understand it better now :-) Regards, Jan -- Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com Losbergenlaan 16, B-3010 Leuven, Belgium From Python to silicon: http://myhdl.jandecaluwe.com |