Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update vga-text-buffer failed link for normal reads and write. #1281

Closed
wants to merge 1 commit into from

Conversation

HamzaRaza786
Copy link

@HamzaRaza786 HamzaRaza786 commented Feb 6, 2024

Previously the hyperlink for 'supports normal reads and writes' in post 3 was redirecting to a page not found, as I guess Stanford has remove that link. So I have added the correct link, which redirects to Stanford's Secure Systems Group, where they have details about CS140 course and relevant pintos docs.

Previously the hyperlink for 'supports normal reads and writes' in post 3 was redirecting to a page not found, as I guess Stanford has remove that link. So I have added the correct link, which redirects to Stanford's Secure Systems Group, where they have the deails about CS140 course and relevant pintos docs.
@@ -60,7 +60,7 @@ The VGA text buffer is accessible via [memory-mapped I/O] to the address `0xb800

Note that memory-mapped hardware might not support all normal RAM operations. For example, a device could only support byte-wise reads and return junk when a `u64` is read. Fortunately, the text buffer [supports normal reads and writes], so we don't have to treat it in a special way.

[supports normal reads and writes]: https://web.stanford.edu/class/cs140/projects/pintos/specs/freevga/vga/vgamem.htm#manip
[supports normal reads and writes]: https://www.scs.stanford.edu/21wi-cs140/pintos/specs/freevga/vga/vga.htm
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The corresponding page under the new URL would be https://www.scs.stanford.edu/21wi-cs140/pintos/specs/freevga/vga/vgamem.htm#manip . But it seems like the "old" URL is also working (again?).

Copy link
Author

@HamzaRaza786 HamzaRaza786 Feb 11, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the correction.Yeah! previously added link is also working now. Will close my PR then.

@HamzaRaza786
Copy link
Author

The change is no more applicable as the corrected link is working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants