NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

- list defaults for BR2_GNU_TARGET_SUFFIX in help text

Browse Source 
- fix a few typos
This commit is contained in:
Bernhard Reutner-Fischer 2006-07-04 11:44:32 +00:00
parent e8609e8ea7
commit c3c100b63f
3 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Config.in
View File

@ -41,7 +41,7 @@ config BR2_x86_64
endchoice
#
# Keep the variants seperate, there's no need to clutter everything else.
# Keep the variants separate, there's no need to clutter everything else.
# sh is fairly "special" in this regard, as virtually everyone else has
# things kept down to a _sensible_ number of target variants. No such
# luck for sh..
@ -259,11 +259,15 @@ config BR2_GNU_TARGET_SUFFIX
other users (most notably ARM EABI) like to add on to this in
order to stay in line with gcc conventions.
Default options are:
linux-uclibcgnueabi for ARM EABI
linux-uclibc for the rest
config BR2_JLEVEL
int "Number of jobs to run simultaneously"
default "1"
help
Number of jobs to run simultanesouly
Number of jobs to run simultaneously
endmenu

2
package/config/Kconfig-language.txt
View File

@ -110,7 +110,7 @@ applicable everywhere (see syntax).
the indentation level, this means it ends at the first line which has
a smaller indentation than the first line of the help text.
"---help---" and "help" do not differ in behaviour, "---help---" is
used to help visually seperate configuration logic from help within
used to help visually separate configuration logic from help within
the file as an aid to developers.

6
target/device/Sharp/LNode80/kernel-patches/001-patch-2.4.26-vrs1
View File

@ -1515,7 +1515,7 @@ diff -urN linux-2.4.26/Documentation/cpufreq-old linux-2.4.26-vrs1/Documentation
+
+CPUFreq architecture drivers are the pieces of kernel code that
+actually perform CPU frequency transitions. These need to be
+initialised seperately (seperate initcalls), and may be
+initialised separately (separate initcalls), and may be
+modularized. They interact with the CPUFreq core in the following way:
+
+
@ -20140,7 +20140,7 @@ diff -urN linux-2.4.26/drivers/char/clps711x_keyb.c linux-2.4.26-vrs1/drivers/ch
+ * Basic Function:
+ *
+ * Basicly the driver is interrupt driven. It sets all column drivers
+ * high. If any key is pressed, a interrupt occures. Now a seperate scan of
+ * high. If any key is pressed, a interrupt occures. Now a separate scan of
+ * each column is done. This scan is timer based, because we use a keyboard
+ * interface with decoupling capacitors (neccecary if you want to survive
+ * EMC compliance tests). Always one line is set high. When next timer event
@ -20150,7 +20150,7 @@ diff -urN linux-2.4.26/drivers/char/clps711x_keyb.c linux-2.4.26-vrs1/drivers/ch
+ * pressed. If any is pressed we reschedule the scan within a programmable
+ * delay. If we would switch back to interrupt mode as long as a key is pressed,
+ * we come right back to the interrupt, because the int. is level triggered !
+ * The timer based scan of the seperate columns can also be done in one
+ * The timer based scan of the separate columns can also be done in one
+ * timer event (set fastscan to 1).
+ *
+ * Summary: