You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
-
2This isn't a direct answer to improving the write speed, but maybe you can cross compile on a machine with more horsepower and just copy the binaries over rather than building software on anemic little ARM boxen?Kevin– Kevin2017-08-15 18:40:01 +00:00Commented Aug 15, 2017 at 18:40
-
1You're right that cross-compiling is much faster, and I use that when I can, but the poor write speeds affect things other than just compiling software. For example, I would like to use the boxes to read and write disk images to SD cards, but like I said writing a 1GB image to an SD card takes more than an hour, while it takes under a minute on an x86 PC.millinon– millinon2017-08-15 18:42:01 +00:00Commented Aug 15, 2017 at 18:42
-
Typically those kernels are a specific version "hacked" for the board. Forget about upgrades...Rui F Ribeiro– Rui F Ribeiro2017-08-15 20:28:35 +00:00Commented Aug 15, 2017 at 20:28
-
I was lucky enough to get the source for the kernel from the manufacturer, so I was thinking that it could be possible to essentially diff the manufacturer's version with the original Linux source, and 'apply the diff' (it would be much more complicated than that of course) to a newer kernel source. That would probably be quite a bit of work, though, so I think I am stuck with the kernel I have.millinon– millinon2017-08-15 20:44:24 +00:00Commented Aug 15, 2017 at 20:44
-
1SD cards are slow, but minutes has to be a bug. Have you checked if there was a bug fix to the SD card driver after that kernel version was forked? Which version is it exactly, which manufacturer?Gilles 'SO- stop being evil'– Gilles 'SO- stop being evil'2017-08-15 22:26:04 +00:00Commented Aug 15, 2017 at 22:26
|
Show 3 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. shell-script), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you