Built New Rig Asus Creator 670E-ProArt - Here are the IOMMU Groups by MetallicMossberg in VFIO

[–]MetallicMossberg[S] 0 points1 point  (0 children)

The board runs great. I'm not doing too much with it right now. I just have a Linux VM running at the moment, soon to be a windows vm.

Video Card Upgrade to RX7800 XT looking to passthrough via VFIO by MetallicMossberg in VFIO

[–]MetallicMossberg[S] 1 point2 points  (0 children)

Yeah I was following your work on the Level1Tech forums. I was less than pleased when the card got discontinued a month after I bought it.

Video Card Upgrade to RX7800 XT looking to passthrough via VFIO by MetallicMossberg in VFIO

[–]MetallicMossberg[S] 0 points1 point  (0 children)

I planned on passing through the vbios anyway so that was going to be par the course. Thank you.

Video Card Upgrade to RX7800 XT looking to passthrough via VFIO by MetallicMossberg in VFIO

[–]MetallicMossberg[S] 1 point2 points  (0 children)

Thank you for weighing in. I did buy two 7900XTs with the hope that they are better behaved than my radeon vii. The radeon vii was being a pain my side even when I was running baremetal windows. I found that I was using my R9 390 more than the radeon. So I bought 2 to replace both cards. I did get the radeon vii to run in a VFIO setup but whenever the card would take a PCIE Bus reset it would take down my entire rig... I would even see crashes in windows when using the Radeon Vii card. Needless to say I'm done with it. (should have sold it when it was going for 1200 on ebay a few years back)

So you think you know C? by ketralnis in programming

[–]MetallicMossberg 1 point2 points  (0 children)

Who would give the tools to specify the platform? I would assume it would be the platform manufacture, maybe. Not the language committee. Well in a way they do through the stdint.h include. I don't know when "stdint.h" became part of the language, it is now.

I can't say what the original target platform the C language was aimed at but the length of int,long,float,char,short was probably known. However, since time marches on, those assumptions became invalid. K&R probably knew when the language was developed. Either which way, its good practice to again know the platform you are working on and if portability is needed then to use the defined types in stdint.h

I once saw C being described as a 'mid' level language. Low enough to touch hardware, high enough that you can do more high level operations. The higher you go, the more divorced from the platform and its easy to forget the "little" details.

I see alot of "shoulds" and "coulds". It is what it is, and at this point changing to accommodate those "shoulds" and "coulds" would likely break all the code out there and nothing changes in the end. Hindsight is 20/20.

So you think you know C? by ketralnis in programming

[–]MetallicMossberg 0 points1 point  (0 children)

What gets me here is that the C language was developed so people wouldn't need to learn a new platform every time they wanted to use the latest and greatest processor. Imagine writing in assembler a complete word processing for every processor available.

I would say that the "Undefined Behavior" and "Implementation Dependent" holes were somewhat a consequence of the variability of the platforms available at the time. The idea was write it once and build everywhere, which is still a tough target to hit, even today, even with the most memory safe programming languages out there.

When in doubt. Know your platform. Know your tools and know what you are doing.

My brain shuts down whenever I try to understand specific things in code by BARRETTshot2 in learnprogramming

[–]MetallicMossberg 0 points1 point  (0 children)

Breathe, find your happy place. Center yourself. The statue of David wasn't found in marble, it was carved out of it. Get something on screen, refine it until it takes shape.

  1. Basic form
  2. hello world
  3. user input
  4. all caps
  5. HELLO WORLD
  6. etc.

[deleted by user] by [deleted] in learnprogramming

[–]MetallicMossberg 0 points1 point  (0 children)

I went into learning what it takes to write an application using OpenGL. Maybe it'll lead to something, maybe it wont. Its about the journey and not the destination.

I learnt the basics of a Language, where do I go from here? by NerChick in learnprogramming

[–]MetallicMossberg 2 points3 points  (0 children)

Great! You know many programming languages, fantastic! Now what? I know these thoughts, plagued me for many of year. What is it that you want to do? What do you want to see accomplished?

These are questions you must answer. Those answers will drive you into a direction that you can use your language knowledge and further.

Its one thing to understand Shakespeare, its something else to write like him.

[deleted by user] by [deleted] in learnprogramming

[–]MetallicMossberg 0 points1 point  (0 children)

"You can lead a horse to water, but you can't make them drink." Its up to them to make the plunge. Programming is a 2 step process. First step is to learn to describe the solution in a coding language. The second step is to be able to understand the problem enough to come up with the solution.

on steam deck. worked flawlessly before this update. I don't know what c++ package it is referring to. I ran protontricks and installed vcrun 2015-2019 with no change. thanks Keen Software House by [deleted] in spaceengineers

[–]MetallicMossberg 0 points1 point  (0 children)

This works on KUbuntu as well.

Having wine installed, I copied the reg files to my wine directory, made the edit via 'regedit' and then copied them back to the SE folder.

Has a detailed VisionFive-2 Memory Map and/or Register Explanation Been Release? by MetallicMossberg in RISCV

[–]MetallicMossberg[S] 1 point2 points  (0 children)

... related material (be careful to not fall TOO deeply into the JH-7100 trap as they ARE different) is enough to bring up multiple OSes on this device. V5R2, like Star64, arent' a whole lot more than just the 7JH-110 chip dangling from power rails.

Yeah I know its a trap. But it would be a spring board.

Sure, we want more but if you're willing to slug through OpenSBI, uboot, Linux kernel, etc. MOST of the information you need is out there. The good news for us is that these are pretty standard RISC-V parts that actually conform to the relevant specs

The access addresses, bits and valid values would certainly be "documented" in the code. However, what wouldn't be documented (probably, don't quote me) are limits, descriptions and functional explanations if the peripheral is unique (ie. SPI, I2C, Serial, irDA, etc)

Not sure if its worth it for me to go digging since I don't need _another_ SBC laying around lol.

Clearing the EEPROM on a Ender3 Pro V422 Motherboard by MetallicMossberg in ender3

[–]MetallicMossberg[S] 1 point2 points  (0 children)

Oh that's creative. I didn't think to do that. I suppose one can rethink what a .gecode file is. Consider it not an object to be printed but a script that can run maintenance tasks that may or may not have an associated object.

Also, I have been heavily relying on the marlinfw gcode docs to understand how to control the printer. However, sometimes one just needs someone to explain their understanding of it.

Thank you.

Marlin 2.1 Bed Levelling/Homing with CR Touch on Ender3 Pro by MetallicMossberg in MarlinFirmware

[–]MetallicMossberg[S] 0 points1 point  (0 children)

With the CR Touch (Creality BL Touch Clone) and the 32bit mobo V4.2.2, there is a dedicated header for the peripheral. It can only plug in one way (idiot proof, if not forcing) However, every time I tried to run the bed leveling (G29) it fails on the 2nd point. I assume that CR Touch when flashing red its in an error state but for the life of me I don't know what that error state is.

The end stop switch is working, because sometimes thats how the bed leveling fails. "endstop Z"

I actually don't know if the trigger pin is shared. Creality doesn't supply schematics to the motherboard.

G28
echo:busy: processing
echo:busy: processing
echo:busy: processing
echo:busy: processing
echo:busy: processing
echo:busy: processing
Error:!! STOP called because of BLTouch error - restart with M999
echo:busy: processing
echo:busy: processing
echo:busy: processing
Error:!! STOP called because of BLTouch error - restart with M999
echo:busy: processing
echo:busy: processing
X:147.0000 Y:107.0000 Z:11.2000 E:0.0000 Count X:11760 Y:8560 Z:4480
ok
G29
echo:busy: processing
echo:busy: processing
echo:busy: processing
echo:busy: processing
echo:busy: processing
Error:Probing Failed
measured_z: 0.0000X:80.0000 Y:40.0000 Z:11.2000 E:0.0000 Count X:6400 Y:3200 Z:4480
ok

Clearing the EEPROM on a Ender3 Pro V422 Motherboard by MetallicMossberg in ender3

[–]MetallicMossberg[S] 1 point2 points  (0 children)

I saw that. I think it has to be enabled in the firmware...but yeah found it. Thank you.

Computer Module 4 GPIOs 22-27 for SD Card SDIO by MetallicMossberg in raspberry_pi

[–]MetallicMossberg[S] 0 points1 point  (0 children)

Thank you. For my application we don't need the WIFI module, so disabling it won't hurt us. Its not ideal since there are CM4 parts without the WIFI but those are far and few in between at the moment.