Panda ES2.0: Correct mem arguments for 1gb
Bug #629269 reported by
Ricardo Salveti
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| jasper-initramfs (Ubuntu) |
Fix Released
|
Undecided
|
Ricardo Salveti | ||
Bug Description
As we now have 1gb support for Panda ES2.0, we should use the correct boot arguments, instead of just mem=463M.
Related branches
lp:~rsalveti/ubuntu/maverick/jasper-initramfs/fix-629269
- Oliver Grawert: Pending requested
-
Diff: 570 lines (+507/-0) (has conflicts)11 files modifieddebian/changelog (+150/-0)
debian/compat (+1/-0)
debian/control (+22/-0)
debian/copyright (+24/-0)
debian/jasper.install (+2/-0)
debian/jasper.triggers (+1/-0)
debian/rules (+3/-0)
debian/source/format (+1/-0)
hooks/jasper (+30/-0)
scripts/local-bottom/jasper_setup (+127/-0)
scripts/local-premount/jasper_growroot (+146/-0)
| Changed in jasper-initramfs (Ubuntu): | |
| assignee: | nobody → Ricardo Salveti (rsalveti) |
| status: | New → In Progress |
Revision history for this message
| Ricardo Salveti (rsalveti) wrote | #1 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in jasper-initramfs (Ubuntu): | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Propose to merge to change mem=463M to mem=460M@0x80000000 mem=512M@