[05:02] <happydays> i take it that the fat.ko and vfat.ko for my marvell arm processor is the bootloader so what does .ko stand for?
[05:07] <happydays> ok, thanks for the help i found out .ko means kernel object file
[05:09] <happydays> so does fat.ko seach the input/output and vfat.ko point to the actual OS
[05:10] <happydays> or vice-versa
[05:12] <scientes> happydays, fat.ko doesn't have support for long file names
[05:12] <scientes> while vfat does
[05:12] <scientes> fat is only 7.3 file names
[05:16] <happydays> scientes: ok but for an arm processor you wouldn't need much anyway
[05:16] <scientes> happydays, it has nothing to do with the processor
[05:17] <scientes> like, a mobile phone uses 7.3 safe file names
[05:17] <scientes> **digital camera
[05:17] <scientes> when it uses the fat filesystem
[05:17] <happydays> doesn't it act as a bootloader for the arm?
[05:18] <scientes> happydays, that doesn't concern the kernel
[05:18] <scientes> thats uboot code, if you are using that sort ofsetup
[05:18] <scientes> (my sheevaplug just uses a flat uImage partition, and then ubifs)
[05:18] <happydays> oh
[05:18] <happydays> forgot
[05:18] <scientes> sure you can also access i from linux
[05:19] <scientes> but i dont have any comp with that sort of bootloader
[05:20] <scientes> fat is a VERY simple filesystem
[05:20] <scientes> both with and without long file names
[05:21] <happydays> cool ok thanks
[05:22] <scientes> and for that reason it appears in alot of embedded devices
[05:22] <scientes> ...and bootloaders
[05:30] <happydays> i was just running my arm machine got side track on what i was doing and completely forgot about the uboot cause i got into the machine at the password and not the boot lol
[05:39] <happydays> BTW sheevaplug's are great inexpensive devices great for learning the in's and out's of embedded systems