I disagree with Charles and Schooner. I used console access for years and I have had enough of it. I am tired of typing long lines of console entry to avoid the conveniences of a good gui interface. There are many features available in a good gui that help avoid carpal tunnel syndrome. I think the HDMI interface should be enabled by default. You can run MachineKit via ssh on another machine with decent 3D acceleration but having a gui interface on the DE10 still has value. If you want to talk about slow go back to a 2mHz Z-80.
You can avoid a half a billion lines of gcode by using a code generator that uses subroutines where possible instead of straight inline code. Alan On Friday, September 1, 2017 at 8:58:59 AM UTC-7, Charles Steinkuehler wrote: > > On 9/1/2017 10:43 AM, schoo...@btinternet.com <javascript:> wrote: > > > > On 01/09/17 15:45, Charles Steinkuehler wrote: > >> ...but since it's already working, I think programming the FPGA via > >> overlays should remain supported for folks who aren't trying to use > >> things like HDMI. > > > > My thoughts for what they are worth. > > > > I would have no intention of ever using HDMI from a board with 1GB > > SDRAM and no GPU. > > > http://www.terasic.com.tw/cgi-bin/page/archive.pl?Language=English&CategoryNo=205&No=1046&PartNo=2 > > > > > I am not sure we should even encourage it by making it available! > > Just asks for loads of "Axis locks up when I load my half billion line > > printer file" threads. > > I would never recommend using the HDMI out for Axis, that's just > asking for problems. Some of the other light-weight UI's might be OK, > but I doubt it. People forget how slow CPU bit-banged displays can be > (and most of the young folk have never even used one). > > > It certainly needs to be able to be disabled or not used, with > > preferably the inconvenience of reboot etc. being for those seeking to > > use HDMI :-P > > I think HDMI should be disabled by default, or possibly in a text-only > console mode (I could actually see that being useful). I agree > enabling any sort of graphics output ought to require at least a > reboot, and possibly a compile (or installation) of a different FPGA > image. > > I think there are some open-source text-mode displays that could be > compiled into the FPGA that have Linux drivers and could be tied to > the HDMI output... > > ...but again, I'm not particularly worried about getting HDMI output > working at all. I think effort is currently better spent on things > like fixing up the hm2_soc_ol driver and automating the uSD image > creation. > > -- > Charles Steinkuehler > cha...@steinkuehler.net <javascript:> > -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
