myhdl-list Mailing List for MyHDL (Page 50)
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
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Christopher F. <chr...@gm...> - 2014-07-04 12:33:07
|
On Fri, Jul 4, 2014 at 6:50 AM, André Prado <and...@gm...> wrote: > So, I can't use the same signal as a signal and a variable. Just like VHDL > :) > Not sure what you mean? You can mix the signal assignment and variable assignment in VHDL? If you declare a signal you need to use "<=" if a variable ":=". MyHDL only has one assignment operator, "=". But the types need to match. You need to determine if you really want a signal or a variable: http://www.jandecaluwe.com/hdldesign/signal-assignments.html > > What is the difference between assigning a value with [:] and without it? > All the intbv values need a [:] ? > In Python everything is a reference x = intbv(0, min=-4, max=4) y = intbv(0, min=-8, max=8) # ... x = 2 y[:] = 4 assert isinstance(x, intbv) # will fail assert isinstance(y, intbv) # will pass The [:] indicates you are updating the value of the intbv type (updating all the bits). If you didn't do this you would loose the intbv information, because the reference would be assigned to another type. But in our HDL we need to know the types we are dealing with (we remove some of the dynamicism :) Yes, all "variable" intbv need "[:] = <new value>". I made changes to your original and it converts, but I did not check if it still passes the testbench: http://www.edaplayground.com/x/eW Note: conversion to Verilog will fail to compile with a Verilog compiler because some of the signal/variable names are reserved words (e.g. "real"). It has been on our todo list to check for reserved words in conversion. Regards, Chris |
From: André P. <and...@gm...> - 2014-07-04 11:50:35
|
So, I can't use the same signal as a signal and a variable. Just like VHDL :) What is the difference between assigning a value with [:] and without it? All the intbv values need a [:] ? Thank you Christopher, Will get back to if you if I get more errors hehe On Fri, Jul 4, 2014 at 8:28 AM, Christopher Felton <chr...@gm...> wrote: > <snip> >> >> >> KeyError: 'real_reg' and a long traceback list error >> >> The module is not 100% functional yet, It's the first time I am doing and >> I confess I am struggling with this different paradigm, It's not VHDL and >> it's not Matlab, it's somewhere in the middle hah. >> >> > One issue, "real_reg" is being used as a variable (real_reg[:]) and as > a signal (real_reg.next). If you resolve this inconsistency it might > fix the error. > > The testbench must not exercise those branches, otherwise you > should of had an attribute error. > > Regards, > Chris > > > > ------------------------------------------------------------------------------ > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > _______________________________________________ > myhdl-list mailing list > myh...@li... > https://lists.sourceforge.net/lists/listinfo/myhdl-list > > -- Atenciosamente/Regards André Castelan Prado |
From: Christopher F. <chr...@gm...> - 2014-07-04 11:28:56
|
> > <snip> > > KeyError: 'real_reg' and a long traceback list error > > The module is not 100% functional yet, It's the first time I am doing and > I confess I am struggling with this different paradigm, It's not VHDL and > it's not Matlab, it's somewhere in the middle hah. > > One issue, "real_reg" is being used as a variable (real_reg[:]) and as a signal (real_reg.next). If you resolve this inconsistency it might fix the error. The testbench must not exercise those branches, otherwise you should of had an attribute error. Regards, Chris |
From: Christopher F. <chr...@gm...> - 2014-07-04 11:24:16
|
When you are using the "tuple of ints" they cannot be used directly in an expression - you can do the following: c_gain = gains[int(num_iteracao)] tmp_mul_gain_imag[:] = (c_gain * imag_reg) << 16 tmp_mul_gain_real[:] = (c_gain * tmp_real) << 16 You will have to do something similar with the angles as well. This will get you past the first set of errors, I didn't verify that the testbench still worked with the changes. This is an example of a simple FIR (sum of products) where the coefficients (h) tuple of ints needs to be separately referenced: https://github.com/cfelton/alt.hdl/blob/master/examples/ex4_mathsop/myhdl/sop1.py Regards, Chris On Thu, Jul 3, 2014 at 4:58 PM, André Prado <and...@gm...> wrote: > Hello everyone, > > I am trying to start with MyHDL! I have FPGA design experience with VHDL > in the old school style. > > I am trying to implement my Cordic module which works in VHDL (Converts > from REAL/IMAG to MAG/ANG) > > However I am getting this error when I try to convert to VHDL: > > KeyError: 'real_reg' and a long traceback list error > > The module is not 100% functional yet, It's the first time I am doing and > I confess I am struggling with this different paradigm, It's not VHDL and > it's not Matlab, it's somewhere in the middle hah. > > > This is my testbench: http://pastebin.com/zqRQxbGL > > This is my Cordic module at the moment: http://pastebin.com/tRU85uwe > > The testbench seems to be OK but I can't generate the VHDL, > > Thank you very much; > > > > > -- > Atenciosamente/Regards > André Castelan Prado > > > ------------------------------------------------------------------------------ > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > _______________________________________________ > myhdl-list mailing list > myh...@li... > https://lists.sourceforge.net/lists/listinfo/myhdl-list > > |
From: André P. <and...@gm...> - 2014-07-03 21:58:51
|
Hello everyone, I am trying to start with MyHDL! I have FPGA design experience with VHDL in the old school style. I am trying to implement my Cordic module which works in VHDL (Converts from REAL/IMAG to MAG/ANG) However I am getting this error when I try to convert to VHDL: KeyError: 'real_reg' and a long traceback list error The module is not 100% functional yet, It's the first time I am doing and I confess I am struggling with this different paradigm, It's not VHDL and it's not Matlab, it's somewhere in the middle hah. This is my testbench: http://pastebin.com/zqRQxbGL This is my Cordic module at the moment: http://pastebin.com/tRU85uwe The testbench seems to be OK but I can't generate the VHDL, Thank you very much; -- Atenciosamente/Regards André Castelan Prado |
From: Christopher F. <chr...@gm...> - 2014-07-03 00:20:12
|
On 7/1/14 7:41 PM, Colin Beighley wrote: > Hello, > > The link http://sourceforge.net/mail?group_id=91207 posted on > http://www.myhdl.org/support/community.html appears to be broken. I'd like to > sign up for the mailing list, any chance someone can fix this? > Thanks for the heads up, you can find the info you need here http://dir.gmane.org/gmane.comp.python.myhdl which is the link at the bottom of the community page http://www.myhdl.org/support/community.html Regards, Chris |
From: Christopher F. <chr...@gm...> - 2014-07-03 00:14:44
|
On 7/2/14 4:18 PM, Colin Beighley wrote: > Hello, > > I'm wondering what the best way of doing a synchronous set in MyHDL is. > Since there doesn't seem to be a built-in equivalent of > @always_seq(clk.posedge, rst) for synchronous sets, is the following > best practice? Let me know if it's bad practice to embed html. > > def qff_w_set(clk, set, q0, q, d): > > @always_seq(clk.posedge) > def logic(): > if set: > q.next= q0 > else: > q.next= d > > return logic > > Thanks, > Colin > > Yes, that is a reasonable approach. Regards, Chris |
From: Colin B. <col...@gm...> - 2014-07-02 21:18:16
|
Hello, I'm wondering what the best way of doing a synchronous set in MyHDL is. Since there doesn't seem to be a built-in equivalent of @always_seq(clk.posedge, rst) for synchronous sets, is the following best practice? Let me know if it's bad practice to embed html. def qff_w_set(clk, set, q0, q, d): @always_seq(clk.posedge) def logic(): if set: q.next = q0 else: q.next = d return logic Thanks, Colin |
From: Colin B. <col...@gm...> - 2014-07-02 00:45:14
|
Hello, The link http://sourceforge.net/mail?group_id=91207 posted on http://www.myhdl.org/support/community.html appears to be broken. I'd like to sign up for the mailing list, any chance someone can fix this? Colin |
From: Jan D. <ja...@ja...> - 2014-06-10 16:02:59
|
I have just published an edited version of an essay that was published earlier on APP and then disappeared with it. Using a concrete example, it explains some of the ideas about HDL design that I feel quite strong about. http://www.jandecaluwe.com/hdldesign/thinking-software-rtl.html I have also published it on reddit, it is possible that it triggers an interesting discussion over there. http://www.reddit.com/r/programming/comments/27skdh/thinking_software_at_the_rtl_level/ -- Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com Python as a HDL: http://www.myhdl.org VHDL development, the modern way: http://www.sigasi.com World-class digital design: http://www.easics.com |
From: Henry G. <he...@ca...> - 2014-05-26 15:48:45
|
On 26/05/14 16:36, Christopher Felton wrote: >> > >> >Yeah, I'm aware of this problem and I haven't quite worked out the >> >solution. I'm hoping there is an adequate simulation model for the >> >blocks I need that aren't encrypted (simple things like the DSP48) until >> >I can justify an expensive license for modelsim or something. >> > >>> >>ps. If it is specifically a question of Xilinx IP, then you could >>> >>implement co-simulation for isim (which Xilinx provides for free). I >>> >>don't know how much work that would be, it depends on whether isim >>> >>supports VPI. >> > >> >As far as I can tell, VPI is not supported. I shall report back if I >> >find out something interesting! >> > > I concur, I don't believe isim supports any foreign language > interfaces, no PLI/VPI/DPI, etc. Something interesting actually occurred to me today - considering a device like a Xilinx Zynq with an on-die ARM Cortex A9, one could actually run a Python test bench on the device itself. This is something that lends itself to Python as it's already running on such a platform. It would be lovely to run the same Python test bench on the device as is being used for development - at least on the system level. Cheers, Henry |
From: Christopher F. <chr...@gm...> - 2014-05-26 15:37:33
|
> > Yeah, I'm aware of this problem and I haven't quite worked out the > solution. I'm hoping there is an adequate simulation model for the > blocks I need that aren't encrypted (simple things like the DSP48) until > I can justify an expensive license for modelsim or something. > >> ps. If it is specifically a question of Xilinx IP, then you could >> implement co-simulation for isim (which Xilinx provides for free). I >> don't know how much work that would be, it depends on whether isim >> supports VPI. > > As far as I can tell, VPI is not supported. I shall report back if I > find out something interesting! > I concur, I don't believe isim supports any foreign language interfaces, no PLI/VPI/DPI, etc. Regards Chris |
From: Martin S. <ha...@se...> - 2014-05-25 18:47:38
|
Hi there, > > Yeah, I'm aware of this problem and I haven't quite worked out the > solution. I'm hoping there is an adequate simulation model for the > blocks I need that aren't encrypted (simple things like the DSP48) until > I can justify an expensive license for modelsim or something. > Actually, I got pretty far on the VHDL side using some cosimulation tricks using GHDL (like debugging virtual CPU designs using the standard GNU debugger). But I haven't seen this on the iverilog side yet. Might require quite some coding.. The Xilinx IP is mostly obfuscated, not really encrypted. As long as it doesn't severely violate the VHDL standards, it mostly works. Cheers, - Martin |
From: Henry G. <he...@ca...> - 2014-05-25 09:26:44
|
On 24/05/14 23:38, Per Karlsson wrote: > Usually simulation models for commercial IP:s come as encrypted RTL, > and so far as I'm aware you cannot simulate encrypted RTL in any > currently available tool based on open source. You'll simply have to > fork up the cash for a commercial, closed source, simulation tool. > But if you do, there is nothing preventing you from instanciating the > IP in a MyHDL module using user defined code and then driving it with > a MyHDL testbench using co-simulation. > > The greater question is of course whether an open source tool could in > theory simulate encrypted RTL, but I leave that for people better > versed in cryptography than myself. > It is also not a question with which MyHDL needs to bother itself, > because it has nothing to do with the language. It concerns only the > simulator. > Yeah, I'm aware of this problem and I haven't quite worked out the solution. I'm hoping there is an adequate simulation model for the blocks I need that aren't encrypted (simple things like the DSP48) until I can justify an expensive license for modelsim or something. > ps. If it is specifically a question of Xilinx IP, then you could > implement co-simulation for isim (which Xilinx provides for free). I > don't know how much work that would be, it depends on whether isim > supports VPI. As far as I can tell, VPI is not supported. I shall report back if I find out something interesting! Cheers, Henry |
From: Per K. <bas...@gm...> - 2014-05-24 22:38:36
|
Usually simulation models for commercial IP:s come as encrypted RTL, and so far as I'm aware you cannot simulate encrypted RTL in any currently available tool based on open source. You'll simply have to fork up the cash for a commercial, closed source, simulation tool. But if you do, there is nothing preventing you from instanciating the IP in a MyHDL module using user defined code and then driving it with a MyHDL testbench using co-simulation. The greater question is of course whether an open source tool could in theory simulate encrypted RTL, but I leave that for people better versed in cryptography than myself. It is also not a question with which MyHDL needs to bother itself, because it has nothing to do with the language. It concerns only the simulator. Cheers! Per ps. If it is specifically a question of Xilinx IP, then you could implement co-simulation for isim (which Xilinx provides for free). I don't know how much work that would be, it depends on whether isim supports VPI. On Sat, May 24, 2014 at 3:59 PM, Christopher Felton <chr...@gm...>wrote: > On 5/24/14 5:32 AM, Henry Gomersall wrote: > > Consider the use case in which one wishes to use a piece of > > off-the-shelf IP, which comes with a suitable simulation library (let's > > say some Xilinx IP with a unisim library). > > > > I have a notion that I want to be able to generate an instance of the > > simulated model for incorporation into a MyHDL design, so when run, it > > executes in the cosimulation environment. This would remove the > > requirement to reimplement the logic of an IP block in MyHDL. > > > > In conjunction with user defined code, this would allow a neat way to > > incorporate commercial blocks into the design. > > > > Is all this sensible? Is there a better way to do it? > > > I don't think this would be a small addition/change and I am > not certain if it is possible, it would take some experimentation > etc. > > The solution that I am aware of is to use a module to emulate > the IP but this can take some work to get the timing of the > interfaces and the behavior correct. When creating the module > to emulate the IP you can use the /v*_code/ or /v*_instance/ > to generate the V* to instantiate the IP. > > Regards, > Chris > > > > > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing platform > available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > _______________________________________________ > myhdl-list mailing list > myh...@li... > https://lists.sourceforge.net/lists/listinfo/myhdl-list > |
From: Christopher F. <chr...@gm...> - 2014-05-24 14:00:02
|
On 5/24/14 5:32 AM, Henry Gomersall wrote: > Consider the use case in which one wishes to use a piece of > off-the-shelf IP, which comes with a suitable simulation library (let's > say some Xilinx IP with a unisim library). > > I have a notion that I want to be able to generate an instance of the > simulated model for incorporation into a MyHDL design, so when run, it > executes in the cosimulation environment. This would remove the > requirement to reimplement the logic of an IP block in MyHDL. > > In conjunction with user defined code, this would allow a neat way to > incorporate commercial blocks into the design. > > Is all this sensible? Is there a better way to do it? I don't think this would be a small addition/change and I am not certain if it is possible, it would take some experimentation etc. The solution that I am aware of is to use a module to emulate the IP but this can take some work to get the timing of the interfaces and the behavior correct. When creating the module to emulate the IP you can use the /v*_code/ or /v*_instance/ to generate the V* to instantiate the IP. Regards, Chris |
From: Christopher F. <chr...@gm...> - 2014-05-24 12:46:44
|
Henry, I recreated the doctest repo to make sure there were not lingering effects on previous branches. Hopefully you haven't clone it yet and no harm, otherwise if you did clone, could you reclone https://cf...@bi.../cfelton/myhdl_09dev_doctest And make the changes in the new repo (with the same name :) Regards, Chris |
From: Christopher F. <chr...@gm...> - 2014-05-24 12:38:11
|
On 5/24/14 4:56 AM, Jan Decaluwe wrote: > 0.8 is in maintenance mode. Bug fixes yes, but > new development should be based on 0.9. Otherwize > things are going to be messy. Of course, but I had made the changes on the 0.8 branch when we were doing 0.8 dev. I attempted to leverage mercurial to merge and prune. The only reason I mentioned it was as a heads up and/or a reminder for me I guess to be safe I will manually create a new clone and copy the files over because I am not 100% sure what happened on 0.8. Regards, Chris |
From: Henry G. <he...@ca...> - 2014-05-24 10:32:33
|
Consider the use case in which one wishes to use a piece of off-the-shelf IP, which comes with a suitable simulation library (let's say some Xilinx IP with a unisim library). I have a notion that I want to be able to generate an instance of the simulated model for incorporation into a MyHDL design, so when run, it executes in the cosimulation environment. This would remove the requirement to reimplement the logic of an IP block in MyHDL. In conjunction with user defined code, this would allow a neat way to incorporate commercial blocks into the design. Is all this sensible? Is there a better way to do it? Cheers, Henry |
From: Jan D. <ja...@ja...> - 2014-05-24 10:30:36
|
0.8 is in maintenance mode. Bug fixes yes, but new development should be based on 0.9. Otherwize things are going to be messy. I have recently merged in or handled all outstanding PRs I believe. Jan On 05/24/2014 02:52 AM, Christopher Felton wrote: > On 5/23/14 4:47 PM, Henry Gomersall wrote: >> On 23/05/14 21:55, Christopher Felton wrote: >>> On 5/23/2014 3:04 PM, Henry Gomersall wrote: >>>>> On 23/05/14 20:57, Christopher Felton wrote: >>>>>>>>>>> Would it make sense to convert the code snippets in the Sphinx >>>>>>>>>>> documentation to doctests so this can be picked up automatically? I can >>>>>>>>>>> have a bash at this if desired (certainly, the FSM one above would be >>>>>>>>>>> useful as a doctest). >>>>>>> Yes, I think this is a great idea, I actually have a >>>>>>> start on this. I have a couple sections completed with >>>>>>> doctest. If others agree I can create a PR with my >>>>>>> changes and then you can add to if you like:) >>>>>>> >>>>> Can you do a sibling pull request (I mean, is it possible)? It makes >>>>> sense to not replicate one another's work! Otherwise can you point me at >>>>> the relevant repository and I'll fork that? >>>>> >>> Yes, I can point you to a repo (it will be a little while). >>> I did this awhile ago, the work was originally done on the >>> 0.8dev branch. It will need to be merged to 0.9. >> >> Great, just let me know when you have it. >> >> Cheers, >> >> Henry > > > Here are the merged changes - I don't know if this is > the final version/format desired but it is a starting > point, I merged it to the 0.9dev branch: > > https://bitbucket.org/cfelton/myhdl_09dev_doctest/overview > > One note of caution, I had made these changes a while > back on 0.8 branch. I used mercurial to merge but which > all went well. But when I pushed it back to the repo above > it indicated it had to create a new head. Not 100% positive > if we want the closed/dead/hanging head pushed back to the > main repo. > > If you fork/clone this make sure you update to the 0.9dev > branch > > >> hg up -C 0.9-dev > > Regards, > Chris > > > > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing platform available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > -- Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com Python as a HDL: http://www.myhdl.org VHDL development, the modern way: http://www.sigasi.com World-class digital design: http://www.easics.com |
From: Jan D. <ja...@ja...> - 2014-05-24 10:16:46
|
0.8 is in maintenance mode. Bug fixes yes, but new development should be based on 0.9. Otherwize things are going to be messy. I have recently merged in or handled all outstanding PRs I believe. Jan On 05/24/2014 02:52 AM, Christopher Felton wrote: > On 5/23/14 4:47 PM, Henry Gomersall wrote: >> On 23/05/14 21:55, Christopher Felton wrote: >>> On 5/23/2014 3:04 PM, Henry Gomersall wrote: >>>>> On 23/05/14 20:57, Christopher Felton wrote: >>>>>>>>>>> Would it make sense to convert the code snippets in the Sphinx >>>>>>>>>>> documentation to doctests so this can be picked up automatically? I can >>>>>>>>>>> have a bash at this if desired (certainly, the FSM one above would be >>>>>>>>>>> useful as a doctest). >>>>>>> Yes, I think this is a great idea, I actually have a >>>>>>> start on this. I have a couple sections completed with >>>>>>> doctest. If others agree I can create a PR with my >>>>>>> changes and then you can add to if you like:) >>>>>>> >>>>> Can you do a sibling pull request (I mean, is it possible)? It makes >>>>> sense to not replicate one another's work! Otherwise can you point me at >>>>> the relevant repository and I'll fork that? >>>>> >>> Yes, I can point you to a repo (it will be a little while). >>> I did this awhile ago, the work was originally done on the >>> 0.8dev branch. It will need to be merged to 0.9. >> >> Great, just let me know when you have it. >> >> Cheers, >> >> Henry > > > Here are the merged changes - I don't know if this is > the final version/format desired but it is a starting > point, I merged it to the 0.9dev branch: > > https://bitbucket.org/cfelton/myhdl_09dev_doctest/overview > > One note of caution, I had made these changes a while > back on 0.8 branch. I used mercurial to merge but which > all went well. But when I pushed it back to the repo above > it indicated it had to create a new head. Not 100% positive > if we want the closed/dead/hanging head pushed back to the > main repo. > > If you fork/clone this make sure you update to the 0.9dev > branch > > >> hg up -C 0.9-dev > > Regards, > Chris > > > > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing platform available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > -- Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com Python as a HDL: http://www.myhdl.org VHDL development, the modern way: http://www.sigasi.com World-class digital design: http://www.easics.com |
From: Christopher F. <chr...@gm...> - 2014-05-24 00:52:46
|
On 5/23/14 4:47 PM, Henry Gomersall wrote: > On 23/05/14 21:55, Christopher Felton wrote: >> On 5/23/2014 3:04 PM, Henry Gomersall wrote: >>>> On 23/05/14 20:57, Christopher Felton wrote: >>>>>>>>>> Would it make sense to convert the code snippets in the Sphinx >>>>>>>>>> documentation to doctests so this can be picked up automatically? I can >>>>>>>>>> have a bash at this if desired (certainly, the FSM one above would be >>>>>>>>>> useful as a doctest). >>>>>> Yes, I think this is a great idea, I actually have a >>>>>> start on this. I have a couple sections completed with >>>>>> doctest. If others agree I can create a PR with my >>>>>> changes and then you can add to if you like:) >>>>>> >>>> Can you do a sibling pull request (I mean, is it possible)? It makes >>>> sense to not replicate one another's work! Otherwise can you point me at >>>> the relevant repository and I'll fork that? >>>> >> Yes, I can point you to a repo (it will be a little while). >> I did this awhile ago, the work was originally done on the >> 0.8dev branch. It will need to be merged to 0.9. > > Great, just let me know when you have it. > > Cheers, > > Henry Here are the merged changes - I don't know if this is the final version/format desired but it is a starting point, I merged it to the 0.9dev branch: https://bitbucket.org/cfelton/myhdl_09dev_doctest/overview One note of caution, I had made these changes a while back on 0.8 branch. I used mercurial to merge but which all went well. But when I pushed it back to the repo above it indicated it had to create a new head. Not 100% positive if we want the closed/dead/hanging head pushed back to the main repo. If you fork/clone this make sure you update to the 0.9dev branch >> hg up -C 0.9-dev Regards, Chris |
From: Henry G. <he...@ca...> - 2014-05-23 21:47:29
|
On 23/05/14 21:55, Christopher Felton wrote: > On 5/23/2014 3:04 PM, Henry Gomersall wrote: >> >On 23/05/14 20:57, Christopher Felton wrote: >>>>> >>>>Would it make sense to convert the code snippets in the Sphinx >>>>> >>>>documentation to doctests so this can be picked up automatically? I can >>>>> >>>>have a bash at this if desired (certainly, the FSM one above would be >>>>> >>>>useful as a doctest). >>> >>Yes, I think this is a great idea, I actually have a >>> >>start on this. I have a couple sections completed with >>> >>doctest. If others agree I can create a PR with my >>> >>changes and then you can add to if you like:) >>> >> >> >Can you do a sibling pull request (I mean, is it possible)? It makes >> >sense to not replicate one another's work! Otherwise can you point me at >> >the relevant repository and I'll fork that? >> > > Yes, I can point you to a repo (it will be a little while). > I did this awhile ago, the work was originally done on the > 0.8dev branch. It will need to be merged to 0.9. Great, just let me know when you have it. Cheers, Henry |
From: Christopher F. <chr...@gm...> - 2014-05-23 20:56:10
|
On 5/23/2014 3:04 PM, Henry Gomersall wrote: > On 23/05/14 20:57, Christopher Felton wrote: >>>> Would it make sense to convert the code snippets in the Sphinx >>>> documentation to doctests so this can be picked up automatically? I can >>>> have a bash at this if desired (certainly, the FSM one above would be >>>> useful as a doctest). >> Yes, I think this is a great idea, I actually have a >> start on this. I have a couple sections completed with >> doctest. If others agree I can create a PR with my >> changes and then you can add to if you like:) >> > Can you do a sibling pull request (I mean, is it possible)? It makes > sense to not replicate one another's work! Otherwise can you point me at > the relevant repository and I'll fork that? > Yes, I can point you to a repo (it will be a little while). I did this awhile ago, the work was originally done on the 0.8dev branch. It will need to be merged to 0.9. Regards, Chris |
From: Henry G. <he...@ca...> - 2014-05-23 20:04:41
|
On 23/05/14 20:57, Christopher Felton wrote: >> >Would it make sense to convert the code snippets in the Sphinx >> >documentation to doctests so this can be picked up automatically? I can >> >have a bash at this if desired (certainly, the FSM one above would be >> >useful as a doctest). > Yes, I think this is a great idea, I actually have a > start on this. I have a couple sections completed with > doctest. If others agree I can create a PR with my > changes and then you can add to if you like:) > Can you do a sibling pull request (I mean, is it possible)? It makes sense to not replicate one another's work! Otherwise can you point me at the relevant repository and I'll fork that? Cheers, Henry |