EmbLogic's Blog

i have completed my MDC project succesfully  by using pointer & function.i have done master array,find code length,compression ,enccryption key& decompression for code length 4………

i have done my MDC for codelength 4. created master array ,encryption key ,compressed file n also decompressed file.

i have also done assignment on structures..

i have completed my compression n decompression for codelength 4..n done by using separate functions for masterarray,codelength,encryption key , compression n decompression..

nw am starting up with the same for codelength 2..

n then will optimise the whole using switch case n try 2 form a formula 4 ecery code length compression n decommpression part..

regards-

sumit ahuja

general compression (1 to 7 bit) done

working on decompression.

any symbol in cprog that r use like power or var..like 2*2*2*2*..or 2any symbol4…

Assignment1 Only 2 question are remaining

We are unable to connect wi-fi through fedora 15 and fedora 10 …………..
(12:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g LP-PHY (rev 01))

I have compelted MDC project for codelength 4. Earlier it was linear program ,now i modified it with seprate functions for master array, compression and decompression . In this program i read data first from a text file and made master array, then compress that file an write compressed data in new file called compressfile.txt. For decompress i again read compressed file and start decompress it an dstore it in a decompressed file.txt.

Now working on file which has 2 codelength. Made master for codelength 2.

8 questions are left in assignment 1

6 question ramaing in assignment 1

Assignment1 solve 6 question more

use of file i/o (low level and high level),,,,,,,,,in compression project,,,,,,,,,,,,,,,

in mdc ,compression hav don ……….

This Macro is used by all USB and PCI drivers. This macro describes which devices each specific driver can support. At compilation time, the build process extracts this information out of the driver and builds a table. The table is called modules.pcimap and modules.usbmap for all PCI and USB devices, respectively, and exists in the directory /lib/modules/kernel_version/.

e.g.:-

static struct usb_device_id puzzle_id_table[]=
{
{       USB_DEVICE(VENDOR_ID,PRODUCT_ID)        },
{0,},

};
MODULE_DEVICE_TABLE(usb,puzzle_id_table);

This will add following lines to modules.usbmap

# usb module         match_flags idVendor idProduct bcdDevice_lo bcdDevice_hi bDeviceClass bDeviceSubClass bDeviceProtocol bInterfaceClass bInterfaceSubClass bInterfaceProtocol driver_info
lkm                  0×0003      0×0951   0×1653    0×0000       0×0000       0×00         0×00            0×00            0×00            0×00               0×00               0×0

The macro MODULE_DEVICE_TABLE automatically creates two variables. For the example: MODULE_DEVICE_TABLE (usb, puzzle_id_table); the variables __module_usb_device_size and __module_usb_device_table are created and placed into the read-only data section and the initialized data section of the module, respectively. The variable __module_usb_device_size contains the value of the size of the struct usb_id structure, and __module_usb_device_table points to the puzzle_id_table structure. The puzzle_id_table variable is an array of usb_id structures with a terminating NULL structure at the end of the list.

When the depmod program is run, as part of the kernel installation process, it goes through every module looking for the symbol __module_usb_device_size to be present in the compiled module. If it finds it, it copies the data pointed to by the __module_usb_device_table symbol into a structure, extracts all of the information and writes it out to the modules.usbmap file, which is located in the module root directory.